How we do Architecture at Okta
summary
Okta defines architecture as a dual charter: level up the tech stack and level up the people stack. Architects embed with teams, run an engineering tech radar and architecture round tables, and require written RFCs/RFDs. A concrete win: the extensibility platform rework uses a web‑task router, in‑memory state store and ultimately consistent hashing, grows from 1.5k RPS target to 6.5x and now ~20k RPS, keeps four‑nines SLAs and controls cost.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 4:41The dual purpose Architecture Charter
- 9:46How Okta does Architecture: The Nuts and Bolts
- 13:18Case Study Extensibility
- 28:25Wrap Up
- 29:34Q&A
related talks
44mWhen your boss decides to have an architecture team…
16mEveryone architect!
50mHow is an architect's success measured...
48mDown the Ivory Tower towards Agile Architecture
43mApplying architectural principles, processes, and tools
43mArchitect(ure) as Enabler of Organization’s Flow of Change
07mWhat is Architecture, and Why It Matters
45mArchitecture and the Architect AD2022