clientdb
indie-stack
| clientdb | indie-stack | |
|---|---|---|
| 3 | 4 | |
| 640 | 1,016 | |
| 0.0% | 3.1% | |
| 0.0 | 6.3 | |
| about 1 year ago | 5 days ago | |
| TypeScript | TypeScript | |
| Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
clientdb
-
The Future of the Web Is on the Edge
Replicache (https://replicache.dev/) and clientdb (https://clientdb.dev/) are the only productized versions of this architecture I'm aware of (please do let me know if anyone is aware of others!).
But the architecture itself has been used successfully in a bunch of apps, most notable of which is probably Linear (https://linear.app/docs/offline-mode, I remember watching an early video of their founder explaining the architecture in more detail but I can't seem to find it anymore).
Basically the way authorization works is you define specific mutations that are supported and allowed, with a client-side and server-side implementation. The client side gets applied optimistically and then sync'ed and ran on the server, which applies authorization rules and detects and handles conflicts, which can result in client state getting rolled back. Replicache has a good writeup here: https://doc.replicache.dev/how-it-works#the-big-picture
-
TinyBase v2.0: “the reactive data store for local-first apps”
This looks really cool, love seeing more innovation in this space!
At first glance this seems to be mostly targeted towards single-user apps where each user would have their own database that can be sync'ed to a remote server, but still isolated from data for other users, similar to the CouchDB+PouchDB model?
At least it looks that way since I couldn't see anything around authorization and conflict resolution. Not that there's anything wrong with focusing on this use case, a lot of apps can function perfectly fine this way.
A few other interesting new players:
https://replicache.dev/
https://clientdb.dev/
- ClientDB
indie-stack
-
Need help creating a site with least number of dependencies
Remix Indie Stack! https://github.com/remix-run/indie-stack
-
The Future of the Web Is on the Edge
I'm building an app using fly.io and SQLite and it's pretty interesting.
this indie-stack shows how to use the remix framework, fly.io, SQLite and Prisma together.
https://github.com/remix-run/indie-stack
I think fly.io will only expand their SQLite features with the creator of Litestream onboard. Exciting stuff!
https://fly.io/blog/all-in-on-sqlite-litestream/
-
Add a Global Progress indicator to your Remix app
I bootstrapped a new Remix app using the Indie Stack which already has tailwind installed as we are going to use it in this exercise.
-
Awesome SQLite
remix-run/indie-stack - The Remix Stack for deploying to Fly with SQLite, authentication, testing, linting, formatting, etc
What are some alternatives?
RxDB - A fast, local first, reactive Database for JavaScript Applications https://rxdb.info/
blues-stack - The Remix Stack for deploying to Fly with PostgreSQL, authentication, testing, linting, formatting, etc.
tinybase - The reactive data store for local‑first apps.
sqlite-plus - The ultimate set of SQLite extensions
epic-stack - This is a Full Stack app starter with the foundational things setup and configured for you to hit the ground running on your next EPIC idea.
litestream - Streaming replication for SQLite.
remix-render - A remix stack for deploying remix to render.com with postgres
deno - A modern runtime for JavaScript and TypeScript.
sqlite-viewer - View SQLite file online
go-dqlite - Go bindings for libdqlite
remix-heroku - A remix stack for deploying remix to heroku with postgres
go-sqlite3 - sqlite3 driver for go using database/sql