Building a Multi-Tenant Insurance Platform
summary
CoverWallet becomes Aon accelerates global growth to ~250 engineers and moves from cloning per-market deployments to a unified multi-tenant platform serving 40+ tenants per quarter, after an early forking code base strategy that wins acquisition but creates hard technical debt. Platform work centers on a configuration tool that spawns tenant clones then applies code or config customizations, Core vs Experience team boundaries, shifting QA into team ownership, Datadog per-tenant monitoring, postmortems with follow-ups, and introducing chaos engineering for payment and resiliency tests.
AI-written summary · about
chapters (8)
- 0:00Introduction to CoverWallet
- 2:33Startup growth and challenges
- 7:15Transition to enterprise scale
- 10:03Multi-tenancy solutions
- 11:31Team structure and evolution
- 13:58Stability and incident management
- 17:46Responsibility and architecture
- 20:52Q&A and concluding thoughts
related talks
28mWhat We Learned Designing & Securing a Multi-Tenant Developer Platform at The New York Times
12mOptimizing Multi-Tenant SaaS
47mBuilding Trust In The AI Era
38mDeveloping Multi-Tenant Applications
44mHello Multitenancy World!
39mDesigning & Securing Multi-Tenant Runtime Environment at the New York Times
25mMulti-Tenancy Architecture Lessons Learned
22mLearn to Navigate the Perils and Pitfalls of Multi-Tenant Identity...