41–50 of 50 posts
I'm happy working on fireproof. The people are very nice. In terms of technology it's a new kind on block. Yes a bit of database and a bit of Blockchain with git rebase.That's why we moving from naming it database to ledger lately.
How does this compare to Dexie js and Dexie cloud?
Many alternatives start with a backend integration mindset, I started from the React hooks and worked towards the storage engine.
Great news! I suspect we'll be using this when we have to go back to on-prem hardware.
The website and example, and usage looks clean. Kudos! I have some questions around what's happening under the hood that werent evident from an initial read of both your website as well as GitHub. 1. Does subscribe listen for new changes on a transient server(just a queue). Or from a more persistent store? 2. Where do the events persist? I didn't see a connector to postgres. I did see one for s3. 3. What is the defau…
These are awesome questions, I'll try to fold the answers into the docs also. 1. The embedded database subscribes to the remote sync endpoint when it is connected. This subscription might be polling, websocket, or anything else. The local embedded database will try to keep up with changes anyone pushes to the remote endpoint. This is more a backend mechanical thing than an API you'll see. Your code can subscribe to t…
hmm. Replicate state to all clients. Ok.
Seems like an opinionated but well thought through project. Godspeed!
Earlier quoted context omitted.
These are awesome questions, I'll try to fold the answers into the docs also. 1. The embedded database subscribes to the remote sync endpoint when it is connected. This subscription might be polling, websocket, or anything else. The local embedded database will try to keep up with changes anyone pushes to the remote endpoint. This is more a backend mechanical thing than an API you'll see. Your code can subscribe to t…
wrt (3) Being able to self-host is extremely important. I noticed a lot of focus on the docs on the Quickstart/client usage. But things like default storage engine as a ENV, path for storage as an ENV. These are very important. hmm. Replicate state to all clients. Ok. Seems like an opinionated but well thought through project. Godspeed!
The vision is many small ledgers, so the full replication per ledger makes sense, but we have work to do on cross-ledger queries
built a lot over couchdb 10y ago and fireproof checks most of the pain points i had with it!
fireproof is super cool! built a lot over couchdb 10y ago and fireproof checks most of the pain points i had with it!