114
Death by a thousand microservices
(renegadeotter.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 12 Sep 2023
114 points (96.0% liked)
Programming
17314 readers
103 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
Microservices are not just about scaling and performance but it is a core advantage. To say they have "nothing" to do with it is outright false.
Scalability isn't something you pull out of the pocket when you need it, you must incorporate scalability by design in everything you do. (Same as with security, and testability, etc.)
Microservices are about modular design and decoupling units of code from each other. Having a bunch of pieces of code run together on a monolithic group of resources that you choose to scale vertically becomes a choice not the be-all-end-all way of doing things.
The problem with this approach is that switching from vertical to horizontal is extremely hard if you didn't plan for it from the start. Thinking in monolithics is a very hard habit to break and it's good odds that any platform that is steeped in verticality will be permeated by it at all levels. You can't just come in and switch, you typically end up having to uproot and redesign a lot of things from scratch, which in most cases ends up as a non-starter from a cost perspective.
They have nothing to do with performance. You can improve performance with vertical scaling, which nowadays has a very high ceiling.
It's not a coincidence that startups are advised against going with microservices until they grow considerably. The growth is organizational, and not traffic.
Yes, but you're failing to understand that the bottleneck that's fixed by peeling off microservices is the human one faced by project managers. In fact, being forced to pay the microservices tax can and often does add performance penalties.
I think you're missing the point that more often than not ain't going to need it.
In the rare cases you do, microservices is not a magic wand that fixes problems. The system requires far more architectural changes that go well beyond getting a process to run somewhere else.