Re:Staging is dead: The rise of preview environments
by klooney on Thursday December 22, 2022 @12:39PM
(#34096041)
Schema changes are hard to roll out that way though.
Re:Staging is dead: The rise of preview environments
by andrewmutz on Thursday December 22, 2022 @02:52PM
(#34097739)
We were a B2B product whose multitenancy model was schema-per-customer, so it was no problem for us.
Agree that it would be harder to implement with customers sharing a schema, but you can still have different release pods
Re:Staging is dead: The rise of preview environments
by scubbo on Thursday December 22, 2022 @12:02PM
(#34095581)
> What I've seen done is that the staging environment is skipped, but instead concentric releases are performed on the customers. So released code goes first to a small group of users, and then widens from there if everything looks good.
If you really want to invest in extensive testing, you can do both! Hell, _and_ you can have a load testing environment as well.
Re:Staging is dead: The rise of preview environments
by andrewmutz on Thursday December 22, 2022 @12:07PM
(#34095641)
Yeah, we had tooling to load a snapshot of customer data (with PII removed) into an ephemeral environment for when developers needed data that was more authentic. This worked for performance related work or just for features that needed a complex data model to be useful (ML apps, etc)
What I've seen done is that the staging environment is skipped, but instead concentric releases are performed on the customers. So released code goes first to a small group of users, and then widens from there if everything looks good.