nessie VS dat

Nessie is an innovative open-source catalog that extends beyond the traditional catalog capabilities in the Apache Iceberg ecosystem, introducing git-like features to data management. This catalog not only tracks table metadata but also allows users to capture commits at a holistic level, enabling advanced operations such as multi-table transactions, rollbacks, branching, and tagging. These features provide a new layer of flexibility and control over data changes, resembling version control systems in software development.

Try Nessie https://github.com/projectnessie/nessie - it recently got trino support as well ..

Project Nessie (https://projectnessie.org/) will be the catalog that eventually decouples Iceberg from Hive. At that point, I think it will be a no brainer to go Iceberg over Delta.

The Dremio Sonar query engine can query your data where it exists whether it's AWS Glue, S3, Nessie Catalogs, MySQL, Postgres, RedShift and an ever growing list of sources.

We will also need a catalog to track all of these tables, with the open source Project Nessie we can do just that, and also get great versioning features similar to using Git when developing applications allowing data engineers to practice "data as code" and "write-audit-publish" patterns on their data.

I'm surprised you didn't include things like `dat`[0]

[0] https://github.com/dat-ecosystem-archive/dat

Gun is an opinionated high level and complete solution, it may provide more than what you need. I would think a more modular alternative is suitable, something like using libp2p. Anyway, you should take a look at the dat ecosystem and the ipfs ecosystem. Also, a really neat and clever way to simply do distributed peer discovery, removing the need for a signalling server, is bitboot (it uses mainline DHT).

Dat/Hypercore lets people share data with others, and you can build applications on top of it