Building a Cloud-Native SaaS Product The Hard Way
summary
Explains concrete tradeoffs: automation for DNS, SSL, email, provisioning and billing; choices between Kubernetes + Knative, Lambda/functions, containers or metal based on cost and workload; multi-tenancy options like single-schema, schema-per-tenant, DB-per-tenant and full-instance isolation with examples (10,000 customers vs millions); use of Stripe/Reco rly, Datadog, Atlas; recommends which components to manage vs buy and shows how isolation, cost and operability actually play out in production.
AI-written summary · about
chapters (13)
- 0:00Introduction to SaaS challenges
- 1:08Core principles of SaaS products
- 2:34Automating cloud resource provisioning
- 3:58Managing SaaS back-office operations
- 5:02Recurring billing and subscriptions
- 6:08Multi-tenancy models explained
- 9:00Isolation vs density trade-offs
- 11:26Hybrid multi-tenancy approach
- 12:28Cloud services integration strategies
- 13:11Choosing compute deployment models
- 15:00Managed vs self-hosted services
- 16:28Open source SaaS paradigm shift
- 18:56Q&A and closing remarks
related talks
07mBuilding a SaaS App on Kubernetes
53mStreamline Cloud-Native App Development Using CDEs
50mJourneys To Cloud Native Architecture: Sun, Sea & Emergencies
25mCloud Native Data on K8s: The Good, Bad, and the Unknown
41mCloud Native Security For The Rest Of Us
31mBuilding a FaaS Platform Using CNCF OSS Projects (Knative, Crossplane, Tekton, ArgoCD)
33mWriting Cloud-Native Applications for Kubernetes
43mHow to build your own cloud-native platform on IaaS clouds in 2021
