3 ms·
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 sim
by aledalgrande 3y ago
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.
- hot_gril 3y agoIt'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.
- aledalgrande 3y agoWe 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).
- hot_gril 3y agoDepending on what the service is, I can see how this would work fine, but I don't think this is a common case.