In a situation where 2 apps could possibly share the same database (think blitzjs app with prisma, and possibly a separate NodeJS backend with prisma, that ultimately work together but the backed server does more computational work while the blitz app handles all the web app queries and mutations for the UI engagement, would both apps need to share the same schema.prisma file contents, as I like even if the backend server didn’t touch some of the prisma tables that the front end does, or vice versa, to make sure everything is in sync, would it be smart to keep the two identical?

@Richard Prins 👋 Better to keep the

schema.prisma

repo separate as an NPM package. If you plan on keeping two separate schemas, then only use Migrate from one schema and use

prisma db pull

from another so there’s only a single source of truth.