I feel like the discussion between "monolith" and "microservices" is a false dichotomy.

For a big software company, you don't have to ship a single behemoth monolith, but you don't have have microservices so small that a team of 3 has to manage 10 services.

You can have "right size" services. I don't like to call them micro because they can be fairly big and do multiple things, as long as it makes sense to have them in a single service.

We had services mostly built around deployment requirements. This package runs on the CDN edge, this other one runs centrally on a cluster.