5 ms·
> Pre-live environments are never at parity with production Then you fix that particular problem. Infrastructure as code is one idea just off the top of my hea
by user3939382 5y ago
> Pre-live environments are never at parity with production
Then you fix that particular problem. Infrastructure as code is one idea just off the top of my head.
- crummy 5y agoIs it possible to make staging 100% identical with prod? Load is one thing I can think of that is difficult to make identical; even if you artificially generate it, user behaviour will likely be different.
- user3939382 5y agoI don't work on systems where that factor is critical to our tests, but if I was I would start here (at least in my case since we use AWS) https://docs.aws.amazon.com/solutions/latest/distributed-load-testing-on-aws/distributed-load-testing-on-aws.pdf https://docs.aws.amazon.com/solutions/latest/distributed-loa...
- shakezula 5y agoEasier said than done, obviously. And even with docker images and Infra as Code and pinned builds and virtual environments, it is difficult to be absolutely sure about the last 1% of the environment, and it requires a ton of effort and engineering discipline to properly maintain. Reducing the number of environments the team has to maintain means by definition more time for each environment.
- raffraffraff 5y agoYup. If you have 4 production data centers, I imagine they're different sizes (autoscaling groups, Kubernetes deployment scale, perhaps even database instance sizes). So just build a staging environment that's like those, except smaller and not public. If you can't do that, then I'm willing to bet you can't deploy a new data center very quickly either, and your DR looks like ass.