Infra SaaS Architecture – the hard parts

In a recent blog post ( we gave a long list of reasons why building a control plane for Infra SaaS is tricky. In this video, we walk through an example – from requirements to design, and illustrate why things are always harder than they first appear.

We discussed:
00: 00 – Introduction
02: 00 – The problem: Customer’s credit card expired
05: 30 – What we need to do when the card expired
09: 42 – Pre-expiration steps
13: 21 – Post-expiration steps
18: 27 – SaaS products have many similar flows
20: 30 – The three stakeholders of every SaaS flow
22: 13 – High level architecture direction
23: 31 – The fundamental problem of control planes
24: 00 – Finally going over the architecture diagram
29: 30 – Two different uses for RBAC service
31: 27 – The data plane comes into the picture
33: 00 – Ram improves the architecture
36: 33 – Summary: The hard parts of control planes
41: 00 – Oh, we forgot to explain how to monitor this

You May Also Like