Microservices, Containers and Kubernetes in Ten Minutes
It is possible to build balls of mud either with microservices or larger-sized services.<p>There are pros and cons to both.<p>But when &quot;easier testing&quot; (from OP) is said to be an advantage of microservices specifically...I am not sure what to say.<p>I mean it is not like every test has to test the entire monolith. And it is not like testing each microservice in isolation is always going to be sufficient.<p>It is entirely orthogonal. Of course a well-designed microservice is easier to test than a monolithic ball of mud, but a well designed monolith is also easier to test than a poorly designed spaghetti of microservices.<p>It is as if some people think &quot;good code&quot; and &quot;microservices&quot; are synonyms. No. They are orthogonal.<p>Industry is always going in circles. Fads come and go.<p>In many ways, Cloud Functions are very similar to a horizontally scalable stateless monolith backend. When you break up services small enough, the &quot;monolith&quot; arises again as simply the sum of what you deploy in an organization.