Search posts, tags, users, and pages
Anu Kumar
Senior AI Engineer. LLM agents, RAG, and the infrastructure that keeps them running.
Every SaaS product has to decide where one customer's data stops and the next one's starts. There are three common answers. On a good day they look much the same. They differ in what happens on a bad
StackShortlist
Proof Over Promises.
Shared schema with a tenant_id on every row scales fine until one customer wants their data in a specific region. Did you find a clean way to move a single tenant out to its own database later without downtime?
StackShortlist
Proof Over Promises.
Shared schema with a tenant_id on every row scales fine until one customer wants their data in a specific region. Did you find a clean way to move a single tenant out to its own database later without downtime?