4 ms·
Conversely, I've seen overly complex but "normal" monoliths. Thousands (millions?) of lines of dead code. Three copies of a file, all 80% the same, but only one
by 88913527 5y ago
Conversely, I've seen overly complex but "normal" monoliths. Thousands (millions?) of lines of dead code. Three copies of a file, all 80% the same, but only one in use.
We say one or the other is overly complex, but I think both are knife throwing just with slightly different details. If you can grok system design, microservices are easier to reason about. If you maintain your monolith well, it's easier to reason about.
- disgruntledphd2 5y ago> Three copies of a file, all 80% the same, but only one in use. I too have seen this. The one benefit of monolith in this case is the three files are in the same repo so at least it's (theoretically) easier to standardise on just one. If they're cross-repo duplicates, then it's a little trickier.
- rglover 5y agoThat complexity is due to developer laziness, lack of discipline, and inexperience—not the pattern. And again, it's not monolith vs. microservices. It's "when is each technique best applied and why?"