3 ms·
I also laugh at 30+ microservice projects where almost every service connects to a single oracle database with no sharding/partitioning. Inb4 aws dynamodb outag
by ivanjermakov 11mo ago
I also laugh at 30+ microservice projects where almost every service connects to a single oracle database with no sharding/partitioning. Inb4 aws dynamodb outage.
- connicpu 11mo agoThe number of services at my job that are just grpc wrappers for a database with endpoints that are only accessed by services that have their own connections open to the same database has been driving me insane.
- 4ndrewl 11mo agoIsn't that a microservices 101? No shared databases?
- kstrauser 11mo agoAn important and common exception would be for performance critical reasons, as mentioned elsewhere. Say most of your code's in Python, but you rewrote parts in a faster language. There you're not necessaryily separating them for isolation or encapsulation purposes. It'd be as much of a mistake to force them to hit separate DBs.
- xorcist 11mo agoWasn't it two pizza teams and using the right tools for the right job?