- cross-posted to:
- programmerhumor@lemmy.ml
- cross-posted to:
- programmerhumor@lemmy.ml
You must log in or register to comment.
Still waiting for ISO timestamp support in OmegaStar.
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?
If you aren’t a gigantic company with so many moving parts it would make your head spin… Probably not much? There is a benefit where you can individually scale your services based on need but that feels like overkill for most.
The bottom outermost green one smells like the load bearing Mac Mini
Lol’d.
Also similar energy to the magic switch: https://users.cs.utah.edu/~elb/folklore/magic.html
GET YOUR SHIT TOGETHER, BLUE!
3 of them look the same- beard, hair, blocky head
Same character model but different hairstyles
