Why You Need to Stop Using 'THE' Staging Server
summary
Argument: stop treating a single shared staging server as the first real test. The concrete claim is to spin up one-off pre-staging environments per feature branch using Docker images, docker-compose and Kubernetes, hand those images as the deliverable, and run unit, integration and performance tests against ephemeral replicas. A working demo shows a composition launched, a sharable URL, automated NPM tests and tear-downs via Codefresh, reducing merge conflicts, shortening feedback loops and catching issues earlier.
AI-written summary · about
chapters (19)
- 0:00Intro
- 1:56About Chloe
- 3:12Agenda
- 4:26Timelines
- 5:22Traditional handshake
- 6:00Broken Staging
- 6:37Feedback
- 9:23Containers
- 10:37Unit Tests
- 12:08Microservices
- 13:05Staging like environment
- 15:29Beyonce
- 16:12Docker Image
- 16:34Git Flow
- 20:01Display Preferences
- 20:15Building a Docker Image
- 25:06Live Demo
- 25:46Unit Testing
- 31:21Visualization
related talks
38mWhy You Need To Stop Using "The" Staging Server
36mDesigning Staging Environments
31mAll The World’s A Staging Server
44mDocker and the Path to a Better Staging Environment
47mStaging Systems are Overrated - Docker-Based System Testing
27mAll the World's A Staging Server
32mTesting in Production
16mStaging Environments: A Blueprint for Pre-production