Re:Goodbye Microservices: From 100s of problem children to 1...
by erik_seaberg on Tuesday July 10, 2018 @02:26PM
(#17500857)
If you're going to go microservices, you want service A to use service B's public API (MQ or RPC or whatever), not to quietly depend on the schema B happened to choose. And sharing a database server instance turns overloads into cascading failures, unless the stack is very good at enforcing resource limits on noisy neighbors.
[ Parent
| on HN ]
There are no comments on this comment yet.