Deploy and Destroy: Testing Environments
summary
Builds a self-serve platform called Namespaces that turns environment configs into JSON schemas and CRUD APIs and wires them to Mesos/Marathon, Docker, Traefik, Consul. It guarantees per-namespace DNS isolation, resource vs service ordering, and team-owned data snapshots; prototype takes ~2 weeks, stable in 2–3 months. At scale it runs about 612 containers across 55 environments on 60 agents, spins simple environments in ~1 minute while DB-snapshot setups can take 10–15 minutes.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:30Problem with static environments
- 4:19Key principles for dynamic environments
- 6:29Namespace system overview
- 9:18Environment schema in JSON
- 12:10Self-serve API for environments
- 13:16Service discovery and isolation
- 16:46Network isolation trade-offs
- 18:08GitLab integration demo
- 19:14Implementation challenges
- 22:07Data replication strategy
- 23:11Debugging and observability
- 24:56Testing vs production deployments
- 26:02Treating environments as a product
- 27:30Key takeaways and summary
- 29:20Q&A session
related talks
30mDeploy and Destroy: Testing Environments
40mDeploy and Destroy Complete Test Environments
28mContinuous Integration Testing: Fully Test your Microservices Application, Early and Often
34mTest Environments Management with
34mAre You About to Break Prod? Acceptance Testing with Ephemeral Environments
26mCorralling the CNFs
34mFrom Zero to Hero, Avoiding Monkey Work!
39mMake Cloud Native Chaos Engineering Easier - Deep Dive into Chaos Mesh