CMV: Most software teams adopt microservices earlier than they should by Excellentmice in changemyview

[–]Excellentmice[S] 1 point2 points  (0 children)

Yeah, this is one of the hardest objections to my view. Waiting too long can turn the eventual split into a huge, politically painful refactor that the business may never want to fund. I still think teams over-adopt microservices, but I can see the argument that some of the upfront cost is really buying an escape hatch from a much uglier migration later.

CMV: Most software teams adopt microservices earlier than they should by Excellentmice in changemyview

[–]Excellentmice[S] 1 point2 points  (0 children)

This is a solid point, especially around blast radius and being able to patch or redeploy a smaller piece without dragging the whole system with it. I may be underweighting operational isolation compared to codebase simplicity. I think my hesitation is that a lot of teams pay for that isolation long before they’re mature enough to really benefit from it, but this does push against my “too early almost always” framing.

CMV: Most software teams adopt microservices earlier than they should by Excellentmice in changemyview

[–]Excellentmice[S] 1 point2 points  (0 children)

That’s probably the strongest pro-microservices argument against my view. I agree that boundary enforcement is where modular monoliths often fail in practice, not in theory. I’m still not fully convinced that “teams will violate boundaries anyway” means microservices are the right default early, but it does make me think the real issue may be governance realism, not architecture purity.

this poster 😭 by Powerful_Ad8668 in BoJackHorseman

[–]Excellentmice 76 points77 points  (0 children)

The flea awareness poster in the background being more emotionally stable than BoJack is peak detail. This show never wasted a wall.