3 ms·
> So with this library we have an append only log of events onto which we persist the events as we receive them You could also use any member of the CouchDB fa
by rakoo 11y ago
> So with this library we have an append only log of events onto which we persist the events as we receive them
You could also use any member of the CouchDB family, such as PouchDB for the browser (even as a lightweight desktop solution), or any member for the mobile [0] [1] [2]
[0] https://github.com/couchbase/couchbase-lite-net https://github.com/couchbase/couchbase-lite-net
[1] https://github.com/couchbase/couchbase-lite-android https://github.com/couchbase/couchbase-lite-android
[2] https://github.com/couchbase/couchbase-lite-ios https://github.com/couchbase/couchbase-lite-ios
What could be really interesting is another member as a library; I don't think there exists any, but kafkalite could be the beginning of something...
- flashgordon 11y agoHey rakoo thanks for sharing that. I actually came across this earlier. (Also RocksDB /LevelDB are amazing as embedded key-value stores). My starting point was to see what a pure log would give you and let the application worry about what it did with the events (eg in the messaging case - update the messages in the respective channels with the new content - the channel is just a table in sqlite!) - essentially a way to decouple the processing of events from their transport and persistence.