Fear and Loathing in Vi.Tech: How to Live Without Microservices

on YouTube ↗50m

" summary

Describes replacing a complex ecosystem of three PHP monoliths, numerous background jobs, and mixed Go/PHP services—deployed with Docker, Kubernetes, Terraform and hosted in many GitLab repos—with an architecture that avoids microservices. Explains the operational pain points (long deploys, slow stock updates) and the practical technologies and practices used to run the system without breaking it into microservices.

AI-written summary · about

" chapters (9)

1. 0:00Introduction
2. 1:08Why split monolith
3. 6:09Prototype and results
4. 11:30Building split team
5. 16:50Constraints and service architecture
6. 23:03Code composition and Cobra
7. 31:20Data sync and Kafka
8. 35:41Summary and recommendations
9. 46:12Q&A

" related talks

• 50mFear and Loathing in Vi.Tech: how to live without microservicesKirill Kuzin · Golang Conf 2024
• 53mSolving technical debt of a microservices architectureVaidas, Donatas · Build Stuff 2017
• 57mBuilding Systems that are #neverdoneJames Lewis · GOTO Amsterdam 2015
• 23mDevOps and Legacy CodeOliver Hankeln, Peter Götz · DevOpsDays London 2019
• 20m3 reasons why micro-services aren't the miracle cureLisa Mittmann · code.talks 2023
• 40mSmoothing the continuous delivery path- a tale of two architecturesLyndsay Prewer · Agile on the Beach 2016
• 33mFireside chat - Monoliths, Microservices & Modernization – Practical StrategiesIvan Brezak Brkan, Bruno Kovacevic · Infobip Shift 2021
• 42mHow to f*ck Up Your Development Team with MicroservicesStephan Schulze · SymfonyLive Berlin 2018