Here’s some sad news: staging is a lie and will never be identical to production, because production is unknowable. Trying to replicate it is often prohibitively expensive. But here’s the good news: production can contain multitudes, including features you aren’t ready to turn on or activate yet. You can hide in the dark and do integration testing at the same time.
It’s simplistic to say that you should just kill the idea of a staging server and do everything in production. There are obviously problems with that. You need to do unit testing; you need to avoid things that will take down a service; and you may need to do essential cutovers. But it’s worth examining what benefit you’re getting from staging and whether you could reallocate that effort.
Join Heidi Waterhouse for an exploration of the ways that you might be able to kill staging and perform better.
Heidi Waterhouse is a developer advocate with LaunchDarkly. She delights in working at the intersection of usability, risk reduction, and cutting-edge technology. One of her favorite hobbies is talking to developers about things they already knew but had never thought of that way before. She sews all her conference dresses so that she’s sure there is a pocket for the mic.
For exhibition and sponsorship opportunities, email SAconf@oreilly.com
For information on trade opportunities with O'Reilly conferences, email partners@oreilly.com
View a complete list of O'Reilly Software Architecture contacts
©2018, O’Reilly UK Ltd • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • confreg@oreilly.com