[SquishyPanda23]

It's usually not obvious where to put the seams ahead of time so you can cut them when you need to split into microservices.

Plus keeping the API boundaries clean costs time and resources, and it's tempting to violate them just to launch this one feature. This extra discipline doesn't have any payoff in the short term, and it has unknown payoff in the long term because you're not sure you drew the boundaries ahead of time anyway.

So I think in practice what happens is you create a monolith and just eat the cost of untangling it when the team gets too big or whatever.