Why You Need To Stop Using "The" Staging Server
summary
Argument: the staging server model breaks down for microservice stacks so replace it with ephemeral, per-branch environments built from container images. Implementation: build and push Docker images, spin up full app stacks with docker compose, orchestration via Kubernetes and Helm charts, run unit, integration, Selenium and JMeter tests against the ephemeral environment, then tear it down. Result: tests shift left, fewer staging surprises, images carry test metadata (demo shows automatic launch and successful runs).
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:06Speaker backgrounds
- 2:10What is Codefresh
- 2:53Traditional CI/CD challenges
- 6:45Problems with staging servers
- 9:38Containers revolutionize pipelines
- 10:45Basic container benefits
- 12:34Microservices and staging
- 14:50Shifting tests left
- 17:23Advantages of Docker images
- 18:49Improved Git flow
- 21:42Demo introduction
- 23:06Creating a pipeline
- 24:50Pipeline details and images
- 25:58Pre-staging environments
- 27:44Launching pre-staging
- 29:29Complex environment demo
- 31:15Multi-stage builds
- 32:41Monitoring pipelines
- 34:05Running environments
- 35:33Q&A session
related talks
36mWhy You Need to Stop Using 'THE' Staging Server
36mDesigning Staging Environments
44mDocker and the Path to a Better Staging Environment
47mStaging Systems are Overrated - Docker-Based System Testing
31mAll The World’s A Staging Server
27mAll the World's A Staging Server
42mUse Docker to test microservices
28mContinuous Integration Testing: Fully Test your Microservices Application, Early and Often