> So, as a blunt statement - your experience is typical. That is, it's average.
Definitely a fair judgement and would agree that this constitutes poor architecting on many many companies' parts including ones that I've been a part of.
> Every one of our 100+ components maintained by our dozen person team can be run and tested on its own.
Can you elaborate on this? What is the primary benefit of running 100-300 components vs a monolith specifically with a 12 person team?
More directly, what's wrong with a monolith at the dozen person team size?
Definitely a fair judgement and would agree that this constitutes poor architecting on many many companies' parts including ones that I've been a part of.
> Every one of our 100+ components maintained by our dozen person team can be run and tested on its own.
Can you elaborate on this? What is the primary benefit of running 100-300 components vs a monolith specifically with a 12 person team?
More directly, what's wrong with a monolith at the dozen person team size?