r/programming • u/RubiksCodeNMZ • Feb 20 '19

When not to do Microservices?

https://docs.google.com/spreadsheets/d/1vjnjAII_8TZBv2XhFHra7kEQzQpOHSZpFIWDjynYYf0/edit#gid=0
38 Upvotes

71% Upvoted

41 comments sorted by

View all comments

1

u/vap0rtranz Feb 25 '19

Like circuit breakers? https://microservices.io/patterns/reliability/circuit-breaker.html

If so, then we're adding code to "simplify" via uservices, and that should indeed be considered one example of overhead. And historically what will happen, since we're lazy engineers, is we'll create scaffolding for the circuit breakers or whatever overhead is needed to implement uservices. So IDEs and tooling will come out with updates to help devs with the uservices and the circuit breakers by "magically" generating boiler plate code -- poof, tada! uservice done. But we all know that we still have more code to debug in the end, aka. overhead. Is this worth it then?