Re:Simple Systems Have Less Downtime
by LargeWu on Tuesday March 03, 2020 @10:00AM
(#22474931)
Microservices, often, is just another word for "distributed monolith". Sure you can read the code of a single service quickly, but often in practice it's not possible to just make changes to one service. There are usually both explicit and implicit dependencies that span many service layers. What you gain in readability I think you often lose more in maintenance overhead.
[ Parent
| on HN ]
Re:Simple Systems Have Less Downtime
by nickbauman on Tuesday March 03, 2020 @10:58AM
(#22475573)
I worked on a microservices practice (with over 400 microservices by the time I left) where it definitely was not a "distributed monolith". I could change all kinds of individual services that did not require changes to other services.
I think monoliths can be written the same way such that you can change one module without changing the others. Microservices enforce that best practice.
"Enforce" gets thrown around a lot, but that's approaching silver bullet expectation levels, in my opinion.
A core skill problems on a team that would prevent building a maintainable monolith do not go away because you've added more things for them to manage.