

You know, this really has me pondering my projects architecture. We have tiers of services.
At the top, we have the UI. Then we have a “consumer” an “orchestra” and a “data” tier.
Data is the tier that exclusively talks to databases. Orchestra talks to the multiple data services. A good chunk of business logic is here. Consumer uses the orchestra and handles UI requests.
All it essentially does is split the monolith into 3 services at minimum. And since it’s on the cloud, there’s a start up cost where we need to spin up 3 machines instead of whatever you can do with microservices. What benefit do I get?


That’s actually a great point that I did overlook.