6 ms·
> Why have a single database when we can silo our data across 200 mini databases? First, many orgs using, say, Kubernetes still run their database separately i
by hdjjhhvvhga 4y ago
> Why have a single database when we can silo our data across 200 mini databases?
First, many orgs using, say, Kubernetes still run their database separately in a traditional way with replicas etc. Second, those who do run their DB inside Kubernetes, probably using an operator, gain scalability and additional resiliency (it also depends on the DB, but these days even PostgreSQL operator works quite reliably).
- sidlls 4y agoA common pattern in microservices architecture is that each service has its own database: that's what the person is referring to.
- hdjjhhvvhga 4y agoWell, I'm of the same opinion as the guy that wrote this short piece in 2018: https://oprearocks.medium.com/blasphemy-multiple-microservices-shared-database-f525025a8a81 https://oprearocks.medium.com/blasphemy-multiple-microservic... Insisting on always having a separate db for each service is not a pattern, it's pure madness.