See first caveat listed here.

Solutions

1. Using one database file per user

Each database would take the user id for its name. There would be at least 2 problems to solve though:

1. How to delete the database files automatically when not in use anymore? Otherwise they would just accumulate in a folder.

2. You would have to restrict characters used for the user_id (no question marks for instance).

I am not sure this would work and how to test it properly. I think solution 2. is better.

2. Refactoring dash_database with redis

It will be hard to achieve the same level of convenience. It is apparently possible to start redis programmatically. You'll still have to install it though (to be fair this is quite a minor inconvenience).

Instead of refactoring we could create a DashDatabaseRedis class (perhaps also rename DashDatabase to DashDatabaseSqlitedict). If redis is not installed we could print some instructions to install it and reraise the usual exception when redis is not installated.

I'd be happy to hear your feedback about this issue (and about this library in general)!