Consider using d1 as storage backend rather than kv

[Enter-tainer]

https://developers.cloudflare.com/d1/platform/pricing/

cloudflare launches d1 recently. It is a cloud native sqlite solution. The free tier allows 100000 writes per day. This is 100x more than kv.

I think we can create a table with only 2 columns, one for key, the other one for value. So we can still expose a kv interface. So we only need change https://github.com/yunsii/cf-worker-status-page-pro/blob/master/src/worker/_helpers/store.ts

[Enter-tainer]

https://developers.cloudflare.com/d1/platform/limits/ One thing to notice is that the max row size is 1MB. This is smaller than kv.

[yunsii]

Furthermore, support to switch storage solution (KV/D1/R2) is a better solution, I migrated the storage to R2 in my company 😂 and it is low priority for now, but PR is welcome.

[Enter-tainer]

r2 is pretty cool. It also has large r/w quota. And it has a much higher limit for object size.

I migrated the storage to R2 in my company 😂

Just being curious, will you open source relevant code here?

[yunsii]

Yes, I will migrate to Pages firstly 😏

[Enter-tainer]

that's fascinating! waiting for your code🥰

[yunsii]

After I tried, Cloudflare Pages does not support Cron Triggers for now.

I think it is so complicated if used with another separate worker, so I decided to wait for its support 😂 And try to support #5 firstly.

[JoyceBabu]

You should enable Smart Placement when using D1, or else the requests will be painfully slow when the worker node is at a different location from the D1 node.