@gsandrew No, I don't think so, because if that is true, Spring Boot, Rails, Django, and any other monolith that didn't have hot swap would die right along with it. My opinion is there is nothing wrong with monoliths to start, but if left unchecked for too long, they can become unwieldy and hard to scale. Then you're left with the task of iteratively trying to break the monolith into smaller services/microservices, which can scale better. Conversely starting with microservices might lead to a lot of overhead that isn't necessary when starting a project. Something I've seen with all projects I've worked on is that they all have legacy code that was written early on in the company's history, that didn't follow good coding practices or take advantage of the framework that was being used or didn't keep up to date with updates. Those types of problems usually contribute to load times but can be cleaned up.