The new key namespace protects configuration consistency but sends checkout reads back to the origin.
The rollback preserves familiar behavior; the Worker change preserves the namespace migration and removes the extra round trip.
Who you’d be doing this for
“I spent the morning explaining why inventory checks suddenly became the slowest part of checkout.”
Karangwa Barasa · Checkout Platform Engineer
She maintains the customer’s checkout API and is paged when eligibility calls slow completed purchases.
What is at stake
Checkout p95 latency is 690 ms after origin eligibility reads rose from 3% to 19%. You must weigh a reversible Worker-side pattern against a rollback that protects today’s change window.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- checkout speed vs namespace consistency
- origin protection vs eligibility freshness
- fast rollback vs reusable edge pattern
Why Cloudflare
Cloudflare Workers and Cloudflare KV sit directly on the request path that determines whether checkout logic stays close to users.
Written with these in mind
Not your kind of problem? 51 more at Cloudflare, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.