
Monolith vs Microservices

#18 - Succeeding in Tech & Cloud Latest - Kelsey Hightower
Topic 8 of 12
Published Dec 7, 2020 · Clip 42:46–54:21 (11:35)
Kelsey explains his 2020 monolith prediction was an observation: Istio itself consolidated its microservice components (Mixer, Pilot, Galley) into a single service for simplicity, and engineering blogs describe companies cutting from 20,000 to 2,000 services for better performance and manageability. He argues microservices make sense for organizational alignment (like at Google), but solo developers and small teams should start with a monolith with engineering discipline—modular codebases, clean interfaces, good testing—so splitting later is natural. He notes DNS means everyone is already doing microservices, defines microservices via a pattern for deciding when to keep logic together or split it (e.g., a Java SDK forcing a separate deployable), traces micro back to SOA in the Java/JBoss world, and likens downsizing to moving from a mansion to a one-bedroom apartment: bad habits follow you if you don't fix them.