4 ms·
What you are describing is in my optinion the exact problem happening with almost all microservices. Building an aggregator microservice to join together two se
by tpetry 6y ago
What you are describing is in my optinion the exact problem happening with almost all microservices. Building an aggregator microservice to join together two services is another microservice in a complex microservice landscape...
People on hn seem to hate monoliths, but a monolith with just a few services outsourced to microservices is much easier to handle. No more joining microservice, no more race conditions when trying to do transactional processing over some microservices and all the problems of microservices.
- konschubert 6y agoI agree that a well-maintained monolith is simpler and more stable than micro services. The emphasis is on well-maintained. If you’ve ever had team A write a crazy query and kill the database for team B, you’ll start to appreciate the damage containment and encapsulation that microservices provide. EDIT: Of course there might be other, better solutions to this problem.
- konschubert 6y agoWith “kill the database” I mean things such as transaction deadlocks.