Cloudflare D1
- Dominant language
- JavaScript
- Stars
- 346
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
Went looking for other options for hosting a `Postgres` DB and read the `D1` announcement post:
https://blog.cloudflare.com/d1-open-beta-is-here/
It looks like a _very_ good product/service focussed on performance.
But the pricing _punishes_ success.
i.e. the more rows your DB has the more you pay:
https://developers.cloudflare.com/d1/platform/pricing/
But it's not like in other DB systems where having more than a few millions rows
doesn't incur a penalty other than storage cost and imperceptible query response time increase ...
If your DB has `10k Rows` and the App has `1 request per second`
and there are `30 x 24 x 60 x 60 = 2,592,000 seconds` in a month.
2,592,000 seconds x 10k rows = 25,920,000,000
After the "25 billion/month" included tier,
the next 25 billion will cost:
25,000,000,000 / 1,000,000 x $0.001 = $25/month
If your number of rows increases to `20k` your costs don't just _double_,
because you burn through the "included" tier twice as fast
and then its `€50` for the next `25B Rows`.
Each incremental increase in the number of rows in the DB drives up the cost of _every_ request.
This could get **_very_ expensive _very_ quickly**. 💰
There's definitely a good use case for `D1` ...
But it bugs me to think of building an app and having _accelerating_ costs. 💭
Also, `$0.75 / GB-month` for storage is a bit silly. 💸
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.