In traditional webapp design, we: 1. have one giant database 2. with lots of tables 3. stuff all user data into the same database, in respective tables I am curious about designs where we do _one sqlite db per user_. We create a new sqlite database for each user. Transactions involving multiple users will be expensive but hopefully rare. Transactions involving only a single user should not block anyone else. I am having difficulty finding books / articles / correct-search-term for this type of design. Can anyone point me at books / articles / correct-search-term ? The main focuses are (1) one sqlite db per user and (2) transactions involving multiple users are rare.