> for what could be a monolithic service On larger projects: a) It is sometimes impossible to run the entire application on a laptop. And so having a micro-se

> for what could be a monolithic service On larger projects: a) It is sometimes impossible to run the entire application on a laptop. And so having a micro-service means you can quickly iterate and test before embedding it into the wider system. b) You will commonly run into conflicting transitive dependencies which you simply can't work around. Classic example being Spark on the JVM which brings in years old Hadoop libraries. c) The inter-relationships between component can become so complex that you really want to be able to use canary or green/blue deployment techniques to reduce risk.