The biggest reason eggs are refrigerated in the US is because they’re not vaccinated for salmonella, so refrigeration is needed to inhibit growth. The US was able to do that since they have the infrastructure for end to end refrigeration. It’s not necessarily wrong, it’s just another way to do it. Since salmonella can also be on the outside of the egg they need to be washed, and since they’re refrigerated the loss of the protective layer doesn’t matter. I guess in Europe with the vaccination it also lowers the chance of salmonella on the outside of the egg allowing the outside to remain unwashed and protective of the inside making refrigeration unnecessary. There’s just not enough of a reason to change things in the us now since the refrigeration method is already in place and switching would cost more up front. The main downside is that you can’t eat raw eggs in the US which means some dishes can’t be made, but the vast majority of the US isn’t interested in raw egg dishes anyways.
It’s just not worth it until your monolith reaches a certain size and complexity. Micro services always require more maintenance, devops, tooling, artifact registries, version syncing, etc. Monoliths eventually reach a point where they are so complicated that it becomes worth it to split it up and are worth the extra overhead of micro services, but that takes a while to get there, and a company will be pretty successful by the time they reach that scale.
The main reason monoliths get a bad rap is because a lot of those projects are just poorly structured and designed. Following the micro service pattern doesn’t guarantee a cleaner project across the entire stack and IMO a poorly designed micro service architecture is harder to maintain than a poorly designed monolith because you have wildly out of sync projects that are all implemented slightly differently making bugs harder to find and fix and deployments harder to coordinate.