News for hackers. Stuff that matters.
Re:The Ingredients of a Productive Monorepo by l5870uoo9y on Wednesday May 28, 2025 @02:53PM (#44119385)
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.
Re:The Ingredients of a Productive Monorepo by marcosdumay on Wednesday May 28, 2025 @03:58PM (#44120110)
> in a monorepo package

Hum... Does that phrase mean you don't use anything remotely similar to a monorepo?

Re:The Ingredients of a Productive Monorepo by someone654 on Wednesday May 28, 2025 @03:17PM (#44119662)
Can 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.