Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Which problems were you thinking of?

Cloudflare and fly.io both promise hassle free read replicas and backup. They will both offer only a single node capable of writes, because that’s how SQLite rolls.

This is a pretty good fit for a read heavy load that requires SQL and very low latency.



I guess I’m not understanding what the benefit is vs hosted Postgres. Also low latency and setup can be equally trivial - see supabase for example.


Biggest benefit over hosted PostgreSQL is that you get SELECT queries that are measured in microseconds, because SQLite avoids needing network overhead per query.

https://www.sqlite.org/np1queryprob.html


Wouldn’t D1 introduce network overhead?


Yes for writes, but it shouldn't for reads: it looks like it works by replicating the full database down to each edge location where the code is running.


Hope this can give you some concrete answers: https://www.sqlite.org/whentouse.html


The important drawback is async replication and therefore the lack of full consistency. On the other hand, this is the big advantage of hosted Postgres and the like.

Those offerings are great for use-cases that don't need that kind of consistency, which are many.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: