[{"data":1,"prerenderedAt":70},["ShallowReactive",2],{"term-m\u002Fmulti-tenancy":3,"related-m\u002Fmulti-tenancy":58},{"id":4,"title":5,"acronym":6,"body":7,"category":40,"description":41,"difficulty":42,"extension":43,"letter":44,"meta":45,"navigation":46,"path":47,"related":48,"seo":52,"sitemap":53,"stem":56,"subcategory":6,"__hash__":57},"terms\u002Fterms\u002Fm\u002Fmulti-tenancy.md","Multi-Tenancy",null,{"type":8,"value":9,"toc":33},"minimark",[10,15,19,23,26,30],[11,12,14],"h2",{"id":13},"eli5-the-vibe-check","ELI5 - The Vibe Check",[16,17,18],"p",{},"Multi-tenancy is how one app serves hundreds of different customers without building hundreds of separate apps. The question is always how much you let those customers share: one giant database with a tenant_id column stuffed on every table, a separate schema per customer, or fully separate databases, and that choice quietly decides how painful your next security bug or noisy-neighbor incident will be.",[11,20,22],{"id":21},"real-talk","Real Talk",[16,24,25],{},"Multi-tenancy is an architecture where a single application instance serves multiple customers (tenants) while keeping their data logically isolated. Common patterns include a shared database with a tenant_id discriminator column, one schema per tenant, or fully isolated databases per tenant, each trading off cost, isolation guarantees, and operational complexity differently.",[11,27,29],{"id":28},"when-youll-hear-this","When You'll Hear This",[16,31,32],{},"\"We started with shared tables and a tenant_id, now big customers want their own schema for compliance.\" \u002F \"A noisy tenant on the shared database was slowing down everyone else's queries.\"",{"title":34,"searchDepth":35,"depth":35,"links":36},"",2,[37,38,39],{"id":13,"depth":35,"text":14},{"id":21,"depth":35,"text":22},{"id":28,"depth":35,"text":29},"architecture","Multi-tenancy is how one app serves hundreds of different customers without building hundreds of separate apps.","advanced","md","m",{},true,"\u002Fterms\u002Fm\u002Fmulti-tenancy",[49,50,51],"Row-Level Security","Sharding","Schema",{"title":5,"description":41},{"changefreq":54,"priority":55},"weekly",0.7,"terms\u002Fm\u002Fmulti-tenancy","omNTDFHeB4GhiEnOcBFNYKcUXFTZaNPBN2FDnfx0HQE",[59,63,67],{"title":49,"path":60,"acronym":6,"category":61,"difficulty":42,"description":62},"\u002Fterms\u002Fr\u002Frow-level-security","database","Row-level security (RLS) is like having an invisible bouncer on every table row.",{"title":51,"path":64,"acronym":6,"category":61,"difficulty":65,"description":66},"\u002Fterms\u002Fs\u002Fschema","beginner","A database schema is the blueprint of your database — which tables exist, what columns they have, what types they are, and how they relate to each other.",{"title":50,"path":68,"acronym":6,"category":61,"difficulty":42,"description":69},"\u002Fterms\u002Fs\u002Fsharding","Sharding splits your database across multiple servers based on some rule — like user IDs 1-1M on server 1, 1M-2M on server 2.",1792528101666]