We're planning our project release for around Q1 of 2024 too, so we'll wait just after the release o
We're planning our project release for around Q1 of 2024 too, so we'll wait just after the release of D1 in GA. Before, we've used the DO to have a kind of document DB per user. Was useful but all the eviction problem (sharing memory per Classe) make us move to D1 when you've confirmed to me few weeks/months ago that you'll permit kind of unlimited databases in the future. So, now we're full D1 SQL.
Since, I've read in the blog article « D1: beta open » that finally this kind of unlimited databases will be reserved to your WfP clients (enterprise plan of $2,000 / month), so finally may be we need to have one full classic DB for all the users, or to fallback to our old architecture on DO.
Since yesterday ,you've increased from 25 to 50,000 databases per account, it's a big step, and it's only a soft limit, but we need to understood if we take a risk to add this security layer ( 1 user = 1 D1 database, kind of sandbox ), because if we reach for example 50,000 users, we'll be totally trap in a very bad situation.
Since, I've read in the blog article « D1: beta open » that finally this kind of unlimited databases will be reserved to your WfP clients (enterprise plan of $2,000 / month), so finally may be we need to have one full classic DB for all the users, or to fallback to our old architecture on DO.
Since yesterday ,you've increased from 25 to 50,000 databases per account, it's a big step, and it's only a soft limit, but we need to understood if we take a risk to add this security layer ( 1 user = 1 D1 database, kind of sandbox ), because if we reach for example 50,000 users, we'll be totally trap in a very bad situation.
