64 karma · joined February 2, 2020
I generally agree with you - there are too many systems that start off as quick productivity and then you get stuck. So there has to be options and composability in a platform. I really agree that you need to have a way to grow your understanding of the system and evolve it over time - not just chase "quick wins".
I am curious if you found any of my suggestions "too platform-y", since it does sound like we agree in broad strokes about ideal architectures.
This is a good point. Hard to claim that you don't know anything and lost money accidentally through bad accounting, and also claim that the exchange is solvent.
I think this covers both the complexity aspect and the difference between what you get from RLS and what external authz brings to the table (schema, for example).
I do think that RLS is a great way for a company without authz experts to built a multi-tenant MVP safely. I've yet to see a single pre-PMF company that worries about authorization beyond that, this is a series-B concern in my experience.
It sounds like their control/management plane (with the user's database) was dependent on their data plane. So a data plane outage was more challenging to mitigate than it should have been in a decoupled architecture. Good lesson for any architecture.