Hi all! To cut straight to the chase - I’m interes...
# orm-help
h
Hi all! To cut straight to the chase - I’m interested in the scenario of using Prisma for a shared database across multiple GraphQL microservices. I understand the scenario of having a database for each microservice, that’s pretty straightforward. However, having only one database for all my microservices seems a bit tricky and challenging. Regarding the answer to a similar question on GitHub, having a Prisma schema definition as an npm package is in my opinion, impractical - you’d want to regularly update your package across all your applications. Is this considered an anti-pattern in the case of Prisma? Is having a separate database for each microservice (therefore a separate Prisma schema) a far better approach, especially with a gateway graph like apollo federation? Has anyone here had any experience on this topic (or an opinion, for that matter)? Thank you very much! 😊