Re:Dear Staging: We’re Done
by trynewideas on Sunday August 09, 2020 @02:37AM
(#24097770)
> Be it an infra change or application. It should always be like:
> Staging -> Canary -> Production
Ironically, the author says exactly this when she presents on it. Why she wrote this article in this fashion is beyond me.
Re:Dear Staging: We’re Done
by joshuamorton on Sunday August 09, 2020 @03:14AM
(#24097944)
The article is a lot more recent than that presentation, its possible the author's opinion has shifted.
So to "solve" her staging problem, she pushes the complexity of multiple feature flags and branching unto developers? Sounds a bit short-sighted given how quickly those complexities is known to multiply. Who is going to pay down those growing technical debts?
Re:Dear Staging: We’re Done
by yjftsjthsd-h on Sunday August 09, 2020 @12:41PM
(#24100793)
How's canary different?
Be it an infra change or application. It should always be like:
Staging -> Canary -> Production
If you invest time in making the above pipeline automated it will cause less outages.
P.S we use feature flags but it won't solve many other challenges around infra and application changes.
Some examples: - Changing from Classic ELBs to ALBs (We care about latencies so ALBs served 1% traffic in the start) - Zero downtime single mysql master upgrade. (ProxySql) - New k8s controllers. - New metrics adapters.
Staging should be like a playground to test all edge cases before you go to canary and then to prod.