News for hackers. Stuff that matters.
Re:Death by a Thousand Microservices by aledalgrande on Tuesday September 12, 2023 @03:20AM (#37477781)
Exactly. And having more than one source of truth for your data complicates a lot of things.

Where I work we run a massive MySQL database that has a pretty simple sharding rule, so I don't believe that you need to split the database even at scale.

Re:Death by a Thousand Microservices by hot_gril on Tuesday September 12, 2023 @11:09AM (#37482450)
It's not primarily about the size of the DB, it's about what's in it. If your massive MySQL DB is only used by one team, then that's fine. If separate teams' services are speaking through shared tables on it, that becomes a mess of an API easily.
Re:Death by a Thousand Microservices by aledalgrande on Tuesday September 12, 2023 @03:14PM (#37486354)
We have thousands of developers on it. I’m not saying it’s a silver bullet, but it works and it works well. Also, the service writing on it is only one (monolith).
Re:Death by a Thousand Microservices by hot_gril on Tuesday September 12, 2023 @05:36PM (#37488804)
Depending on what the service is, I can see how this would work fine, but I don't think this is a common case.