Davids Slingshot: Leveraging Ory
summary
A legacy CIAM called Goliath stays in place while Ory Hydra becomes a regional OAuth proxy, cutting cross‑region egress and latency and reducing egress costs by ~99%. That change yields no client changes and makes the platform more resilient, enabling the org to move from a few releases a year to 100 deployments/day vs 3–4/year. Next step is swapping Goliath for Ory Kratos incrementally; tradeoffs include glue code, proxy multi‑tenancy work, and eventual consistency. MFA waits on Kratos features.
AI-written summary · about
chapters (9)
- 0:00Introduction to David's Slingshot
- 1:48Speaker's background and project context
- 3:33Brownfield project challenges and Goliath
- 8:32Failed attempts to replace Goliath
- 11:43Discovering Ory and its advantages
- 12:26Integrating Ory Hydra for resilience
- 15:17Plans to replace Goliath with Ory Kratos
- 17:24Benefits and drawbacks of Ory setup
- 18:06Q&A session
