Successful Go for microservices architecture
summary
Migrates a Scala monolith and serverless chain to Go microservices, replacing 1–2s JVM cold starts with cold start drops from 1–2s to milliseconds on Go Lambdas and improving latency for telephony workloads. Uses AWS X-Ray for tracing, Go modules, Ginkgo/Gomega tests, goreleaser and a GraphQL server generator to build and release services. Adopts a per-domain package layout, forbids casual pointer mutation after a prod break, and plans Protobuf and generics for safer contracts.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:13Monolith to microservices with Go
- 3:40Microservices benefits and challenges
- 10:08Go performance in serverless
- 13:40Go ecosystem and community
- 15:51Go standard library
- 18:24Key Go libraries
- 20:55Go tooling and DX
- 21:40New dev onboarding with Go
- 24:10Go limitations and folders
- 26:35Pointers and interfaces in Go
- 28:03Future Go microservices improvements
- 30:06Conclusion and Q&A
related talks
45mGo, Microservices and all the joy!
31mBuilding a microservices architecture with Go
15mDo's and Dont's moving to Golang Microservice Architecture
01h 02mBuilding Microservice Architectures with Go
38mMicroservices in Go using Micro
36mA colorful journey of be from NodeJS to Go
42mScaling Microservices in Go
51mMicroservices in Go