> Unfortunately this is only a marginal improvement, as the team remains devoid of engineering discipline. :/ This strikes me as the crux here, along with this

> Unfortunately this is only a marginal improvement, as the team remains devoid of engineering discipline. :/ This strikes me as the crux here, along with this line from the article: > There were three main reasons for the initial success of microservices as an architectural pattern for software: [...] 3) an excuse for having no architecture. Microservices are a little bit too much of a "just so" story to me. It's a cozy non-answer to the hard problems of system design.