Hi @xiaoyu2er, that comparison is outdated. Workers KV is the fastest way to retrieve data from a Wo
Hi @xiaoyu2er, that comparison is outdated. Workers KV is the fastest way to retrieve data from a Worker, especially for high read throughput.
Workers KV makes use of caching across the Cloudflare network internally to make sure that highly requested items are very fast. That means that it's ideal for configuration data, non-relational data, A/B tests, user preferences, that requires very high read throughput (high requests per second) and that have infrequent reads. The caching means that your data is effectively global.
You'd use D1 for your general application data. It can handle lower throughput but provides consistency, which you may need if you want to immediately see writes. This is why it's recommended for general application data.
The big part that is missing from the benchmark above, in addition to it being outdated, is regionality. KV is replicated globally, whereas D1 is currently single-region.
Workers KV makes use of caching across the Cloudflare network internally to make sure that highly requested items are very fast. That means that it's ideal for configuration data, non-relational data, A/B tests, user preferences, that requires very high read throughput (high requests per second) and that have infrequent reads. The caching means that your data is effectively global.
You'd use D1 for your general application data. It can handle lower throughput but provides consistency, which you may need if you want to immediately see writes. This is why it's recommended for general application data.
The big part that is missing from the benchmark above, in addition to it being outdated, is regionality. KV is replicated globally, whereas D1 is currently single-region.
