I am using RethinkDb in one of my project as the main repository for push notifications (web app) in such way that:

1. A table is created for each user
2. When the user goes online, the unreceived notification are pushed
3. The table is watched and new notification are pushed to the user

I believe that creating a table per each user can make querying and monitoring changes much faster. However, it is inevitable that I may end up with thousands of tables. Given that database management is not a problem in case there would be thousands of tables, would this approach cause any performance issues in RethinkDb or is there any limit to the maximum number of table the database can handle?