3 ms·
Few ways we are taking it a step further, one, ofc is an actual well built dashboard with table editors, which makes a huge difference to many devs trying to ma
by yoeven 2y ago
Few ways we are taking it a step further, one, ofc is an actual well built dashboard with table editors, which makes a huge difference to many devs trying to manage their DB with all the tools they need in a UI. Which in comparison Cloudflare UI doesn't do much beyond creating the database for you and the table editors are horrible to use/buggy.
With CF you would need work with D1 within a worker function and manage the balancing of that worker with hundreds micro DBs when you scale which gets very complex. Something we solved to an extent but still more things to build to fully achieve that! Dzero allows you to use SQLite without the lock into the ecosystem of CF, so locally as well without the worker CLI and a bunch of workaround to run your project locally.
While D1 offers cached read data to some of their Edge locations, we took it a step further by cloning SQLite files and actually storing it in S3/R2 instances around the globe with read consistency. This allow for better performance gains and less cold starts of D1 and workers!
Lastly, working around the limits. The limits of 10GB per DB is a hard limit due to the infra, however account limits has "unlimited" scale which CF can unlock at a certain enterprise level. Our goal is to build a form of Horizontal/Vertical sharding similar to planetscale with multiple D1 instances to scale your data with 10GB per DB.