5 ms·
If you can set up a canary, you can set up a staging environment. Once you set up a staging environment, it's a matter of sending the traffic you want to send t
by hayst4ck 4y ago
If you can set up a canary, you can set up a staging environment. Once you set up a staging environment, it's a matter of sending the traffic you want to send to staging. That's trivially done by vending out cookies to those you wish to send to the staging environment.
I don't see much point in staging anything but business logic. I don't see the point in staging in any way that isn't "live."
- 60secs 4y agoStaging environments solve transitivity problems which canaries don't. If your services are very weakly coupled, you can probably get by with canaries. If you have tightly coupled microservices, staging has a lot of opportunity to catch bugs before they get to prod and cause outages. The canary / break prod / rollback attitude is why developers are constantly putting out fires instead of getting things done.
- hayst4ck 4y ago> The canary / break prod / rollback attitude is why developers are constantly putting out fires instead of getting things done. Having a team solely responsible for rollbacks and failed builds is immensely helpful. If you frequently have code that passes tests but fails in prod, then a team must "regulate" the commons (the shared code base).
- jstx1 4y agoIs this common practice? Live staging doesn't sound like staging at all to me, it sounds like prod.
- hayst4ck 4y agoIt's fairly common to continuously deliver to a staging environment and then occasionally choose one of the staged revisions to push to prod. Normally employees would be sent to that kind of staging environment which is very much prod.