this post was submitted on 11 Nov 2025
623 points (98.6% liked)
Programmer Humor
27343 readers
1307 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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?
Separation of concerns is a major benefit that shouldn't be overlooked with security implications. Assuming you are properly restricting access to each worker node / "tier", when one tier inevitably becomes compromised; it doesn't result in the complete compromise of the entire monolith.
That's actually a great point that I did overlook.