3 ms·
Microservices you trade application complexity for devops complexity. My theory is to make devops as simple as possible and push complexity into application co
by andrewstuart 3y ago
Microservices you trade application complexity for devops complexity.
My theory is to make devops as simple as possible and push complexity into application code.
This includes a rule to use cloud VMs but use the minimum possible cloud services, ideally none, especially not things like lambda/ cloud functions.
- corethree 3y ago>Microservices you trade application complexity for devops complexity. There's a second trade off. Overall complexity. The application as a whole is more complex when split into two than when existing as one. So three things happen: 1. Complexity of the individual microservices goes down. 2. Dev ops complexity goes up. 3. Overall complexity of the entire system in general goes up.
- aledalgrande 3y agoAdd data complexity to that (consistency)
- andrewstuart 3y agoYeah great point. Then trying to work out where the problem is spans both DevOps and development and suddenly you are in a world of hurt.
- hosh 3y agoA lot of microservices introduce unnecessary complexity. Erlang and Elixir are unusual in that you can have independent “microservices” running within a monolith.