4 ms·

I think a critical limitation is that the database offering is designed for a very specific philosophy (which, honestly, the rest of the platform is too) and no

by keeda 6mo ago

I think a critical limitation is that the database offering is designed for a very specific philosophy (which, honestly, the rest of the platform is too) and not suitable for general purpose use. The 10GB limit per DB is unsuitable for even trivial use-cases. I was going to use it for a new prototype (because I already use it for other stuff) and I realized the DB limitations could quickly become a blocker even for a prototype. If I understand correctly, the primary philosophy of the platform is edge computing with dedicated infra (workers, DB, etc) per-user. While that may be an under-leveraged niche and CloudFlare excels at it, it is still a niche.

kentonv 6mo ago
To clarify, there are two approaches you can take to handle large-scale databases on Cloudflare: With Durable Objects[0], you can create and orchestrate millions of sqlite databases that live directly on Cloudflare's edge machines. The 10GB limit applies to one database, but the idea is you design your system to split data into many small databases, e.g. one per user, or even one per document. Since the database is literally a local file on the machine hosting the Durable Object that talks to it, access is ridiculously fast. Scalability of any one database is limited, but you can create an unlimited number of them. If you really need a single big database, you can use Hyperdrive[1], which provides connection management and caching over plain old Postgres, MySQL, etc. Cloudflare itself doesn't host the database in this case but there are many database providers you can use it with. [0] https://developers.cloudflare.com/durable-objects/ https://developers.cloudflare.com/durable-objects/ [1] https://developers.cloudflare.com/hyperdrive/ https://developers.cloudflare.com/hyperdrive/ (I'm the lead engineer on Cloudflare Workers.)

by keeda 6mo ago

kentonv 6mo ago

To clarify, there are two approaches you can take to handle large-scale databases on Cloudflare: With Durable Objects[0], you can create and orchestrate millions of sqlite databases that live directly on Cloudflare's edge machines. The 10GB limit applies to one database, but the idea is you design your system to split data into many small databases, e.g. one per user, or even one per document. Since the database is literally a local file on the machine hosting the Durable Object that talks to it, access is ridiculously fast. Scalability of any one database is limited, but you can create an unlimited number of them. If you really need a single big database, you can use Hyperdrive[1], which provides connection management and caching over plain old Postgres, MySQL, etc. Cloudflare itself doesn't host the database in this case but there are many database providers you can use it with. [0] https://developers.cloudflare.com/durable-objects/ https://developers.cloudflare.com/durable-objects/ [1] https://developers.cloudflare.com/hyperdrive/ https://developers.cloudflare.com/hyperdrive/ (I'm the lead engineer on Cloudflare Workers.)