Prisma

I'm a little confused on dividing schemas into services... Let's say we have on one service the authentication schema, with `User`s, `Role`s and such, and another `todo-service` that has `Todo`s and `List`s, and `List`s have a field that references a `User` type; now here's what confusing to me: should I maintain the full Prisma schema on both services? Or maybe that's where stitching to one `api-service` comes to play? I know there's nothing written in stone here, but i'm trying to figure out how to properly decouple everything neatly :stuck_out_tongue:

forgetting prisma, would all these services be talking to one database?

I would recommend a module based approach to separate out domains instead of separate services.

Check out this as an example: <https://github.com/benawad/fullstack-graphql-airbnb-clone/tree/8_register_mutation/packages/server/src>

<@U8ZQADW1H> well the services will be talking to the same Prisma endpoint, and for the moment to the same database

when would you say it's a good time to think on making separate services <@UACPQ70HE> ?