"Modernizing monolithic applications" understood as "rebuild the system as set of microservices" is like assuming that "modernizing your house" means rebuilding it as 10 single-room, tiny houses.
10
32
2
157
Then each of those houses can be build in a different style, can have a different type of heating, you can tear down one of the tiny houses and replace it with something more modern without affecting the others... maybe it's not so bad?
3
1
Is that the set of requirements you'd think of by default when you think of modernizing a house? Most folks I know tore down a wall, renewed the pluming, fresh floors and paint. I've yet to meet someone how dreams of or sees value in different heating systems for different rooms.
2
3
And: sure there'll be situations when what you suggested *is* of value. I just don't get why we accept that assumption so broadly without challenging it.
1
2
Replying to @odrotbohm @lutzhuehnken
Originally it was the other assumption that was challenged, because experience shows that being too big is one of the major reasons for a lot of problems with legacy software. Replacing too few systems (1) with too many (100+) might not be the best solution, of course.

Dec 16, 2021 Β· 4:15 PM UTC
2