LONG LIFE TO VAGRANT… VAGRANT IS DEAD
summary
Five years of real-world evolution: development VMs grow 1GB → 8GB VMs until shared boxes and macOS NFS break things; SMTP is moved to RabbitMQ to decouple SMTP and response times improve; monolith fragments into microservices running in Docker while simple public pages stay on Vagrant only for development of public pages; pipeline uses AWS ECS + CodePipeline; team runs two stacks during migration, migration works but remains incomplete and drives tooling choices by product needs.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 2:12Why this talk
- 5:21What Vagrant is
- 9:37Company in 2013
- 13:14Application growth
- 16:42VM filesystem issues
- 18:13Docker and microservices
- 20:06Changing approach
- 21:14Filesystem crash impact
- 22:18Current stack migration
- 23:46Culture and pipeline
- 26:15Similar environments
- 28:00Modern pipeline setup
- 29:27Choosing tools
- 30:36Q&A
related talks
24mFrom Zero to a Full Docker Based IT Teams
25mVagrant: The Stick and Carrot of a DevOps Leader
31mReady To Code: Automate Your Development Environment
44mVagrant, Packer, Serf: Maximum Potency DevOps
24mEvolution of Unix environments and the road to faster deployments
38mVagrant for real
20mHow fast can you onboard a new team member?
54mReproducible and Portable Development Environments with Vagrant