Fear and Loathing in Vi.Tech: how to live without microservices
summary
A Go-focused talk about moving away from microservices by consolidating a messy stack: three PHP monoliths with long deploys, a mix of Go and PHP background services, many jobs, Docker, Cobra, many GitLab repos, Kubernetes and Terraform. It explains the problems this setup caused (slow deployments, complex coordination) and discusses living without microservices by simplifying architecture and tooling.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:09Monolith problems
- 4:17Why microservices
- 6:03Prototype proof
- 7:11Building platform team
- 9:36Monolith split mistakes
- 11:02Domain models
- 13:54SOA vs microservices
- 16:46Infrastructure limits
- 19:35Go monorepos
- 23:22Approach benefits
- 25:05Service code structure
- 27:17Soft skills matter
- 28:43Builder problem
- 31:10Data sync
- 34:01Summary
- 36:49Q&A
related talks
50mFear and Loathing in Vi.Tech: How to Live Without Microservices
40mKill "Microservices" before its too late
45mGo, Microservices and all the joy!
43mGo micro with Microservices
37mKnee Deep in Microservices
55mMicroservices, Where Did It All Go Wrong
34mLevel up with a Microservices architecture
15mDo's and Dont's moving to Golang Microservice Architecture