Thanks for the example, it helped me understand the idea. The thing that I'm unclear on is how do I figure out what data to ship to the user? Like if I don't a

Thanks for the example, it helped me understand the idea. The thing that I'm unclear on is how do I figure out what data to ship to the user? Like if I don't already have a database-per-user then I have to extract only the data the user has permission to see, and ship that as a database? That would be the case even if I had database-per-customer - not every user is necessarily able to see all the data owned by the organization they're a part of. It seems like a lot of extra work, and error-prone, too (what could be worse than accidentally shipping the wrong data _as an operational database_ to a client?) Edit: the article covers this at the bottom, but IMO it's a show-stopper. How many applications of any real complexity can actually implement database-per-user (database-per-tenant is probably not enough, as I mentioned above). As soon as you need any kind of management or permissions functionality in your app then you can't ship the database anymore, so you may as well start off not shipping it.