4 ms·
Separating out the database layer in a monorepo package was the best architectural decision I made this year. Now it is my default because at some point you eit
by l5870uoo9y 1y ago
Separating out the database layer in a monorepo package was the best architectural decision I made this year. Now it is my default because at some point you either want to rebuild the existing app entirely or separate out services such as public API access that all need access to the same database.
- someone654 1y agoCan you elaborate on this? I’m facing a similar decision in my org and think sharing a common database store sounds smart. With rules of course, like clear ownership of data, only one writer, etc.
- marcosdumay 1y ago> in a monorepo package Hum... Does that phrase mean you don't use anything remotely similar to a monorepo?