zlacker

Bunny Database

submitted by dabina+(OP) on 2026-02-03 12:13:44 | 320 points 136 comments
[view article] [source] [go to bottom]

NOTE: showing posts with links only show all posts
3. ForHac+ns[view] [source] 2026-02-03 14:58:44
>>dabina+(OP)
This sounds a lot like https://turso.tech/ ? Unless I misunderstand, they're both pitching SQLite-for-the-cloud.
◧◩◪◨⬒⬓
29. no_wiz+lM[view] [source] [discussion] 2026-02-03 16:22:15
>>pier25+oJ
Edge computing. Cloudflare workers for example.

Bunny has a similarity concept: https://bunny.net/edge-scripting/

◧◩
35. wahnfr+SR[view] [source] [discussion] 2026-02-03 16:42:43
>>grugde+VQ
Look into the capabilities of what I consider the leading edge of open source RDBMS managed solutions, Yugabyte: https://www.yugabyte.com

And tell me how easily you can achieve this "out of the box"

If you don't care about business continuity or high availability then everything gets easier

> And neither MySQL or Postgres ever seem to go down, they're super reliable and stable

The box they're on goes down

43. cschma+BV[view] [source] 2026-02-03 16:56:55
>>dabina+(OP)
fwiw, Bunny are the people that announced S3 compatibility for their object storage in Q2 2022 [1]

> We can’t wait to have this available as a preview later in Q2 and truly make global storage a breeze, so keep an eye out!

then apologised for missing that in September 2023 [2]

> We initially announced that we were working on S3 support for Bunny Storage all the way back in 2022. Today, as 2023 is slowly coming to an end, many of our customers continue to follow our blog, hoping for good news about the release.

changing the roadmap to early 2024 [2]

> But we are working aggressively toward shipping S3 compatibility in early 2024.

That same post also has the beautiful "At bunny.net, we value transparency." quote. It's early 2026, and they're literally ignoring my support requests asking about what the roadmap is looking like for this now.

So, do not trust their product or leadership at all.

[1] https://bunny.net/blog/introducing-edge-storage-sftp-support... [2] https://bunny.net/blog/whats-happening-with-s3-compatibility...

44. kawspe+FV[view] [source] 2026-02-03 16:57:03
>>dabina+(OP)
I've been struggling with Bunny the last couple of days.

Their log delivery api is delayed by over 3 days, despite them promising only "up to 5 minutes delay" in their docs: https://docs.bunny.net/cdn/logging

Why isn't it on the status page you might ask? Oh, that's because a delay is not "critical", but I fear I am losing loglines now, their retention is 3 days.

It's an interesting strategy for them, because it doesn't inspire confidence in me about their other offerings. When they can't reliably operate a log delivery API or be transparent about issues, it's hard to trust them with something as critical as a database.

◧◩
58. Nnnes+k21[view] [source] [discussion] 2026-02-03 17:27:50
>>4star3+Iu
Disclaimer: I have not used either product; I have used a number of Cloudflare's (mostly free tier) offerings.

In addition to the other points brought up, it looks like pricing strongly favors Bunny once you're outside of Cloudflare's free tier.

Per billion rows read: Bunny $0.30, Cloudflare $1.00 (first 25B/month free)

Per million rows written: Bunny $0.30, Cloudflare $1.00 (first 50M/month free)

Per GB stored: Bunny $0.10/region, Cloudflare $0.75 (5GB free)

Bunny also has a lot better region selection, 41 available vs. Cloudflare's 6 (see https://developers.cloudflare.com/d1/configuration/data-loca...). Even though Bunny charges storage per region used where Cloudflare doesn't, Bunny still comes out cheaper with 7 regions selected. Bunny lets you choose how many and which regions to replicate across; Cloudflare's region replication is an on/off toggle that is in beta and requires you to use "the new Sessions API" (I don't know what this entails).

The main reason I haven't tried out D1 is that it locks you into using Workers to access the database. Bunny says they have an HTTP API.

I plan to stick with VPSes for compute and storage, but I do like seeing someone (other than Amazon) challenge Cloudflare on their huge array of fun toys for devs to play with.

◧◩◪
64. gsande+Kf1[view] [source] [discussion] 2026-02-03 18:17:29
>>fspoet+H21
I'd like it too. The new docs do refer to it e.g:

> When S3 compatibility is enabled (currently in beta), the number of available replication points is reduced

I assume it's a private beta.

https://docs.bunny.net/storage/storage-tiers#s3-compatibilit...

◧◩
72. gordon+ej1[view] [source] [discussion] 2026-02-03 18:29:54
>>mchusm+qK
Same, it's nice to use a no-BS CDN for personal projects (e.g. https://atlasof.space/). Their pricing is good and I actually appreciate that they have no free tier so that there's no "oh shit" moment when you suddenly exceed it and owe real $$$ (looking at you, Netlify). I probably won't use their database feature but I'll for sure keep using their CDN if they can keep things as straightforward as they currently are.
◧◩
73. latefo+nn1[view] [source] [discussion] 2026-02-03 18:44:51
>>grugde+VQ
> Maybe I'm not the target market for this, but how hard is it REALLY to manage a RDBMS?

It is not. You can provision a free Postgres instance with a single click: https://neon.new/

◧◩◪◨
77. latefo+Ct1[view] [source] [discussion] 2026-02-03 19:09:20
>>jonath+qs1
Neon is from Databricks. Here's their pricing page: https://neon.com/pricing
◧◩
88. jorams+TP1[view] [source] [discussion] 2026-02-03 20:49:32
>>kerbla+391
This documentation page[1] seems pretty clear. One primary at a time, any number of read replicas that automatically proxy writes to the primary, when compute scales to zero the data is in object storage and a new primary can spin up elsewhere.

[1]: https://docs.bunny.net/database/replication

◧◩
89. chungy+eQ1[view] [source] [discussion] 2026-02-03 20:51:26
>>koakum+CC
LibSQL doesn't look anywhere close to active enough to consider it for production IMO.

Just compare the most recent commits from LibSQL: https://github.com/tursodatabase/libsql/commits/main/

To those of SQLite: https://sqlite.org/src/timeline

One of these looks like a healthy and actively maintained project. The other isn't quite dead, but it's limping along.

99. Retr0i+y32[view] [source] 2026-02-03 21:59:26
>>dabina+(OP)
The "Wait, what does “SQLite-compatible” actually mean?" subheading didn't answer my question to be honest. They're using (forked) libSQL under the hood - ok, cool. But how do I interface with it?

They don't elaborate, but apparently libSQL has an HTTP API called "Hrana": https://github.com/tursodatabase/libsql/blob/main/docs/HRANA... - if that's what they're exposing, wouldn't it make more sense to call it libSQL-compatible or something?

◧◩
101. tad_to+7g2[view] [source] [discussion] 2026-02-03 23:06:34
>>the__a+pQ
People need to know!

(Context: <https://xkcd.com/1871/>.)

◧◩◪
107. jpeele+9W2[view] [source] [discussion] 2026-02-04 04:02:47
>>chungy+eQ1
Your activity comparison isn't wrong, but it's because they are focused on doing a complete rewrite instead of focusing on the libSQL fork.

https://turso.tech/blog/we-will-rewrite-sqlite-and-we-are-go...

◧◩
119. m_nali+vw3[view] [source] [discussion] 2026-02-04 09:28:57
>>Retr0i+y32
Marek from bunny.net here. To connect to Bunny Database you can use one of the SDKs (TS, Go, Rust, and .NET) or the HTTP endpoint which is documented here: https://docs.bunny.net/database/connect/sql-api
◧◩◪
121. m_nali+Qy3[view] [source] [discussion] 2026-02-04 09:45:14
>>Square+Ks
Marek from bunny.net here. Another advantage is our global network: Bunny Database is available in 41 regions, so if your app has global users (or users in specific locations), you can avoid workarounds to hide latency from the DB.

We actually ran a benchmark to see how read latency degrades with distance from the database: https://bunny.net/blog/how-database-location-affects-far-awa...

[go to top]