News for hackers. Stuff that matters.
Re:Cloudflare is down by ethbr1 on Friday December 05, 2025 @08:42AM (#46161153)
For hypothetical conflicting changes (read worst case: unupgraded nodes/services can't interop with upgraded nodes/services), what's best practice for a partial rollout?

Blue/green and temporarily ossify capacity? Regional?

Re:Cloudflare is down by cryptonym on Friday December 05, 2025 @10:38AM (#46162701)
- Push a version with the new logic but not yet enabled, still using legacy logic, able to implement both

- Push a version that enables new logic for 1% of traffic

- Continue rollout until 100%

Re:Cloudflare is down by nrhrjrjrjtntbt on Friday December 05, 2025 @06:36PM (#46168856)
Can also do canary rollout before that. Canary means rollout to endpoints only used by CF to test. Monitor metrics and automated test results.
Re:Cloudflare is down by cryptonym on Saturday December 06, 2025 @03:45AM (#46171716)
That's ok but doesn't solve issues you notice only on actual prod traffic. While it can be a nice addition to catch issues earlier with minimal user impact, best practice on large scale systems still requires a staged/progressive prod rollout.
Re:Cloudflare is down by nrhrjrjrjtntbt on Saturday December 06, 2025 @03:49AM (#46171731)
Yep. This is definitely an "as well as"

Unit test, Integration Test, Staging Test, Staging Rollout, Production Test, Canary, Progressive Rollout

Can all be automated can smash through all that quickly with no human intervention.