I’ve a doubt regarding Prisma architecture: What is the motivation for placing Prisma inside a docker container rather than it being a library ( like Sequelize, etc)?

Hey Mario, I've recently written up a response to exactly this question (among others) here: https://gist.github.com/nikolasburk/78b1031eca08a3046f6cb92fad0de8d7 Quoting the relevant part: The main reason why the Prisma server exists is because of Prisma's history and the fact that it was born out of Graphcool (which is a Backend-as-a-Service). While we see a lot of potential value in using this additional server component between your database and application server, we definitely acknowledge that it can be confusing for people starting out with Prisma that are "just looking for an ORM". That's why we are currently working on a version of that will make it possible to use the Prisma client without running an additional Prisma server that will be available soon. Nevertheless, we are going to continue to build out the Prisma server as we think that it can add a lot of value in the future, especially for more advanced/enterprise use cases. For example, we're planning to add caching and security capabilities to it. Having this extra layer that sees (and routes) all your database requests (especially if it's connected to multiple databases) is a great place to implement things like audit logging or other features that are critical in the enterprise world. Also note that the Prisma server is horizontally scalable, so it can be deployed as a multi-node cluster as well. Benefits that the Prisma server buys you today already e.g. are the subscription API or that it enables connection pooling when used in the context of serverless functions.

Thank you