4 ms·
Adding micro-services is the way to make the company bankrupt. "micro-services" is the worst solution to ANY problem. Is not a solution, only another way to wr
by mamcx 2y ago
Adding micro-services is the way to make the company bankrupt.
"micro-services" is the worst solution to ANY problem. Is not a solution, only another way to write a problematic app.
The problem here is complexity and "micro-services" is the MOST efficient way to add complexity.
And the real problem here is complexity X scalability, which requires simplicity and tunning, stuff that "micro-services" IS NOT mean to solve.
---
I work in the enterprise space, and you bet you can cut 70%* (every time you find stuff like this) of the code and stay single-master-DB even for some very large companies if you have a half-decent architecture.
p.d: Do note that cut code does not mean the app will end with just 30%, is just that 70% is trash to be redone.
- hot_gril 2y agoAre you saying that every company up to a certain size should have a single master DB?