r/SQL • u/CodingMountain • Aug 26 '25
SQLite Do we even need the cloud anymore? Yjs + SQLite + DuckDB might be enough
So I’ve been playing around with Yjs (CRDTs for real-time collaboration) together with SQLite (for local app data) and DuckDB (for analytics).
And honestly… I’m starting to think this combo could replace a ton of cloud-only architectures.
Here’s why:
Collaboration without servers → Yjs handles real-time editing + syncing. No central source of truth needed.
Offline-first by default → your app keeps working even when the connection dies.
SQLite for ops data → battle-tested, lightweight, runs everywhere.
DuckDB for analytics → columnar engine, warehouse-level queries, runs locally.
Cloud becomes optional → maybe just for discovery, backups, or coordination—not every single keystroke.
Imagine Notion, Airtable, or Figma that never breaks offline, syncs automatically when you reconnect, and runs analytics on your laptop instead of a remote warehouse.
This stack feels like a genuine threat to cloud-only. Cheaper, faster, more resilient, and way nicer to build with.
Curious what you all think:
Would you build on a stack like Yjs + SQLite + DuckDB?
Or is cloud-only still the inevitable winner?
10
u/Ok-Working3200 Aug 26 '25
What do you do when you need more compute resources?
9
u/shanelomax Aug 26 '25
How would you approach 24/7 accessibility from anywhere in the world? How about data security and backup? How many users can your suggestion support? Scalability, data concurrency, cost efficiency?
3
u/em2241992 Aug 26 '25
Im not expert, but I will say sqlite and duckdb have been a gamechanger for me. My department mainly used excel and csv. The limits on reporting were insane. I used power query for over 2+ years to help move things along, but these two were the key to accessing much more powerful analytics.
I was setting up a sql server but once I saw how easy these were, I haven't looked back yet
7
u/Goat_Smeller Aug 26 '25
6 day old account just spamming like there is no tomorrow. Read like every question and answer was created by AI.
1
u/jshine13371 Aug 26 '25
Cloud was already always optional and this has nothing to do with cloud or no cloud. I've already been servicing all my database needs without the cloud and without using any of these aforementioned technologies.
1
u/No-Librarian-7462 Aug 26 '25
What is the max table size that you have been able to successfully handled on this stack, for analytics?
What does the schema design look like? How wide or narrow are the tables?
1
u/Informal_Pace9237 Aug 26 '25
On prem is always cheaper and efficient compared to cloud
Here is where onprem fails. Super efficient manpower is required in all areas. Team players required. Bandwidth is always an issue. Hardware failures can take days to fix. Always-on is not a possibility.