if it's an important project, which "large project" sounds like, then no it's not a good choice.
In the meantime, I suggest you use another database service. For example I'm very excited about D1, but I'm watching my project with planetscale. I'll migrate as soon as I can.
Cloudflare will never give a release date for any product or fix or service. The canned response is always .
Eliminate application bottlenecks by bringing the performance and data portability of open source, lightweight SQL close to your users with low overhead
We’ll be announcing (just announcing: not enabling) pricing in a few weeks, but it’s very much an “it depends” case. DO is key-value based, whereas D1 is a queryable database. If you have a lot of small reads, then D1 is likely to be much cheaper. DO charges on 4KB boundaries. I’d need to know a LOT more about your query patterns here.
DO prices a read & write on 4KB boundaries. Many web-facing database workloads are selecting single rows of user data (500 bytes!), or simple reads to generate lists. These are very small.
We’ll the thing is a database is forever expanding right. If you are constantly adding data to your db you are guaranteed to one day reach that cap. Just trying to understand how one would handle that
Same thing if you hit 50GB? It takes a lot of traditional relational data to add up, and you will be able to create many databases. Each DB will have its own limits.
Sorry if I’m not understanding this correctly as I have mostly worked with DO. Like planet scale I’m pretty sure if you reach your plan limit you just upgrade and get more storage. So with d1 I’m trying to understand what efforts will be required
I think it’s worth stepping back a second. I understand that hitting a storage limit sounds concerning, but… if you have 500 bytes per row, and 10M order rows: that’s just 5GB.
While in the Alpha period, there is a possibility of breaking changes. The Alpha is meant for testing purposes and using it for Production traffic is not recommended.
I’m just going to restate here: D1 is in alpha. A lot will change. I’d love to share more, but much of this is subject to change. Storage limits included.
Yeah my concern is not that it’s in alpha and only 100mb but rather if we can’t expand storage what do we do when we reach limits. Sorry if I’m going in circles I’m new to data storage and just trying to learn. I love CF and a fanboy of all services. Trying to do everything within the ecosystem
As with any DB - you end up potentially splitting/sharding it out - by date or user ID or order ID. Even if you can scale AWS RDS up to 1TB, you often don’t want to do that as it ultimately has performance and risk trade-offs. Same with PlanetScale.
Hi @elithrar, can you give us a steer around how we can expect to handle breaking changes? Is there going to be a compatibility flag/date or will it just stop working?
Cloudflare Workers KV is low-latency key-value storage at the edge. Leverage serverless computing and build serverless architecture with key-value storage.