Topic starter
18/08/2026 2:53 pm
TL;DR: Cloudflare’s move to extend OAuth to all users with Ory Hydra processed 132.5 million row updates, 114.7 million inserts, 22,200 commits, and no session breaks while cutting P95 API latency 45%, according to Ory. The lesson is that identity infrastructure for machine and human access now has to behave like core platform plumbing, not a side service.
Editorial analysis by NHI Mgmt Group, based on content published by Ory: “Ory Hydra Powers OAuth at Cloudflare Scale; and It's Just Getting Started”.
By the numbers:
- Cloudflare’s migration processed 132.5 million rows updated, 114.7 million rows inserted, 136.97GB of temporary storage consumed, and 22,200 transaction commits.
Key questions
Q: How should IAM teams migrate OAuth systems without breaking active sessions?
A: Use a staged cutover with blue-green deployment, replayable queues, and extended token expiry windows so live sessions survive the transition.
Q: Why do large identity migrations create access risk even when the schema update succeeds?
A: Because identity systems are stateful control planes, not static data stores.
Q: What signals show that an auth platform is struggling at enterprise scale?
A: Rising P95 latency, high temporary storage use, growing commit volume, and increased CPU or heap pressure are all signs that the identity layer is approaching operational limits.
Practitioner guidance
- Model identity migrations as stateful cutovers Map token state, revocation state, and session continuity before changing any OAuth or OIDC backbone.
- Validate session preservation during deployment Test blue-green or parallel-run patterns against active user traffic so the old and new identity paths can overlap without breaking logins or silently dropping revocations.
- Benchmark auth latency under load Measure P95 latency, CPU, heap use, and commit pressure during peak authentication and migration windows, then set acceptance thresholds for future identity changes.
Bottom line: Large OAuth migrations can succeed technically while still failing operationally if session continuity, revocation, and token state are not governed as part of the cutover.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
18/08/2026 3:37 pm
Identity infrastructure has crossed the threshold from supporting service to platform dependency: At Cloudflare scale, OAuth is no longer a narrow authentication feature, it is part of the operational fabric of the business. When a migration touches 132.5 million row updates and still has to preserve sessions, access continuity becomes a platform property rather than an IAM afterthought. Practitioners should read this as evidence that identity change management now belongs in core infrastructure governance.
A few things that frame the scale:
- DeepSeek alone generated 113,000 new exposed API keys in 2025, illustrating how new AI providers create credential exposure before security guardrails catch up, according to the State of Secrets Sprawl 2026.
- Only 20% have formal processes for offboarding and revoking API keys, and even fewer have procedures for rotating them, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: When should IAM teams treat authentication as core infrastructure?
A: When login, token exchange, or revocation changes can affect millions of users at once, authentication should be governed like a core platform service. At that point, availability, cutover design, and session continuity are part of identity architecture, not separate concerns.
👉 Read our full editorial: Cloudflare’s Ory Hydra migration shows the cost of OAuth scale