RxDB VS hREA

I'm interested in this problem also!

I think there is a large overlap with projects that market/focus on offline-first experiences.

AFAIK this problem can be solved by:

1) Considering a client-side copy of the database that gets synced with the remote DB. This is an approach [PowerSync](https://www.powersync.com/) and [ElectricSql](https://electric-sql.com/) and [rxdb](https://rxdb.info/) take!

Hey, after I posted that, I went and gave a second look online to see if I could find something that would allow me to develop a local-first app with offline persistence and syncing capabilities.

I ended up finding some possibilities out there that could potentially help me build stuff. One of them is RxDB [1], which offers WebRTC syncing - you'd still need a signaling server, I suppose, but all sensitive information could be synced E2E-encrypted via WebRTC.

Then there's CRDT's [2], which is a universe that turned out to have multiple possibilities that match (at least partially) my needs. In particular, the next thing I want to take a look at is cr-sqlite [3], which might be just thing I needed to kick-off some side-projects.

I'm posting here cause I just found some hope of not needing to build a traditional client-server app and having to deal with all the hassle involved in securing a server (and with fear that my efforts could be not good enough), and I thought someone else could benefit from getting to know these things.

[1] https://rxdb.info/

About a year ago, I discovered a cool offline-first framework called RxDB. Initially, I thought that on the frontend side, this was exactly what I had been searching for over the past years. After tinkering around and even using it in production for some time, I realized that it wasn't well-suited for my intended use. RxDB was initially created as an RxJS layer for PouchDB with a server replication interface. Over time, other storage types besides PouchDB were introduced (e.g., IndexedDB, SQLite) and the replication interface became more sophisticated. The replication interface is really cool and exactly what I wanted. The biggest problem I have with RxDB is that it is so tightly coupled with RxJS. While RxJS is technically very powerful, it offers a dreadful developer experience. It's really hard to understand at first and integrating it into an existing codebase, which isn't using RxJS, is tedious.

Congrats to the team. Once I’ve tried https://rxdb.info/ and it wasn’t funny at all to do the remote replication (PG) and to deal with conflicts. I do need to check this out!

RxDB (Open Source but paid plugins)

If you’re curious, REA stands for Resource-Event-Agent. The h is for Holochain software implementation of that accounting framework. Dive deeper into hREA: 🕸️ Full Ecosystem Session: https://youtu.be/WsIut-gtCvQ 🕸️ hApp spotlight: https://blog.holochain.org/happs-spotlight-hrea-a-private-messenger-app/ 🕸️ GitHub: https://github.com/h-REA/hREA 🕸️ Website: https://hrea.io 🕸️ Get involved: https://discord.gg/um4UsxdFDk 🧩 #HolochainOpenDev 🧩

> Also get tired of the aspirational rants of how it is going to fix supply chains and offer banking to the underserved communities. And yes, I understand banking, supply chains, and crypto enough to know that that will never happen.

agreed. have you heard of hREA [1] and http://valueflo.ws, by Bob and Lynn from http://mikorizal.org? it's sort of an open source SAP alternative, that is designed as local-first software. it uses the REA accounting method [2] to implement LETS or mutual credit type economic networks for cooperatives / small business ecosystem / commons based peer production / any transitional/solidarity economies.

Bonfire is also implementing Valueflows vocabulary on ActivityPub [3].

[1] https://github.com/holo-rea/holo-rea

[2] http://www.jeffsutherland.org/oopsla97/haugen.html

[3] https://bonfirenetworks.org/

are running encrypted app code for them so that they can take part in the app/network, without having the required technical chops (the holofuel currency measures processing power). the FAQ does a good job of explaining it a bit more: https://holo.host/faq/

i'm not super interested in the whole holo thing (they sold holofuel hosting credits). i am glad they did it because it meant the team could ramp up development.

about the marx and engels thing. i am most excited about the potential for http://valueflo.ws on top of holochain [3], because it will allow us to move away from today's Enterprise Resource Planning (ERP) software, into a new paradigm of Network Resource Planning (ERP) software, that i hope will have a big impact on supply chains of the next economy (socialist).

[1] https://github.com/holochain/holochain

[2] https://www.indiegogo.com/projects/holo-take-back-the-intern...

[3] https://github.com/holo-rea/holo-rea

Check out the holochain project as well as valueflo.ws/hREA projects. There is a lot of work being done on "next-economy"/post-capitalist technology in the "web3" space. Some other people to check out in that space are Arthur Brock and Mikorizal software.

Might want to check out the Holo-REA github for the latest implementation of some of these ideas being built on Holochain: https://github.com/holo-rea/holo-rea

Example, Valueflo.ws is based on, if I understand it correctly, Resource-Event-Agent (REA) accounting, as an alternative to traditional double entry bookkeeping, and an implementation of these are ideas are currently being built on Holochain, as Holo-REA.

Something that really blew my hair back is hREA - a combination of the Resources Events Agents (REA) accounting method, with the distributed application framework holochain. It's fully open source: https://github.com/holo-rea/holo-rea

This is a fun intro: http://mikorizal.org/futures.html

Check out Valueflo.ws / hREA (formerly HoloREA): https://github.com/holo-rea/holo-rea