A case for microservices

on YouTube ↗18m

" summary

Argues that Go plus microservices produce a virtuous cycle that increases developer confidence and happiness and that the right constraints pay off. Cites ~30% adoption signal, heavyweight costs of distribution and testing, and benefits like bounded context and consumer driven contracts. Describes building gokit as a toolkit of circuit breakers and rate limiters, instrumentation and transports to make microservices safe in large orgs and claims it eases deployment and iterative change.

AI-written summary · about

" chapters (11)

1. 0:00Introduction
2. 1:05Microservices' bad reputation
3. 2:34Microservices challenges
4. 5:02Go’s hidden strengths
5. 7:30Microservices as constraints
6. 9:39Bounded context in DDD
7. 11:25Software’s true goal
8. 13:54Building confidence via architecture
9. 15:17Go kit for microservices
10. 16:44Resistance to change in teams
11. 17:04Closing

" related talks

• 45mGo, Microservices and all the joy!Andrzej Grzesik · NDC London 2017
• 31mGo + Microservices = Go KitPeter Bourgon · Golang UK 2016
• 39mGo + Microservices = Go KitPeter Bourgon · CloudNativeCon + KubeCon Europe 2017
• 31mBuilding a microservices architecture with GoJorge Lorenzo · GoLab 2019
• 38mMicroservices, a bittersweet symphonySebastian Sogamoso · RailsConf 2015
• 38mMicroservices in Go using MicroBrian Ketelsen · Codemotion Milan 2017
• 47mimport Golang; struct microservicesGiulio De Donato, Giorgio Cefaro · Codemotion Rome 2015
• 55mMicroservices, Where Did It All Go WrongIan Cooper · NDC London 2025