gdb

Hi everyone, I’ve been building *GenosDB (GDB)*, a peer-to-peer graph database with zero-trust security baked into the core. *Why*: most P2P apps end up relying on centralized servers for identity and access control. GDB enforces trust cryptographically, peer-to-peer. *Features*: * P2P sync via WebRTC/relays * Eventual consistency with cryptographic checks * Reactive queries with live updates * Role-based access control + ACLs * Data encrypted per-identity *Note*: proprietary, but free to use without restrictions. Repo: [github.com/estebanrfp/gdb](https://github.com/estebanrfp/gdb) Examples: [Use cases & samples](https://github.com/estebanrfp/gdb/blob/main/docs/genosdb-exa...) I’d love feedback, stress testing, and ideas for the roadmap. –– Esteban Fuster Pozzi (estebanrfp) Examples: [Use cases & samples](https://github.co

GenosDB isn’t aiming to replace TigerGraph, Neo4j, JanusGraph, Dgraph, or ArangoDB in traditional server-side workloads. It takes a different direction: • Runs entirely in the browser (no backend) • Clients are the source of truth • Peer-to-peer sync via WebRTC • WebAuthn + RBAC for authentication • Local storage via OPFS • Lightweight bundle It targets edge-native, local-first, and real-time apps, not centralized graph clusters. Performance: Fast local queries, sync latency depends on peers Latency: Near-zero for local ops; sync varies Scalability: Horizontal, client-based Modularity: Built with pluggable components (e.g., auth, AI query) Flexibility: Ideal for dynamic, offline-capable, decentralized apps If you’re building a modern, peer-first system—GenosDB is a better fit than traditional server-side graph DBs. Repo: https://git

Considering the intrinsic limitations of distributed systems, GenosDB performs well. I’ll share some examples in case you’d like to try them out. https://github.com/estebanrfp/gdb/wiki/EXAMPLES.md

I'll send you the complete documentation, it's super easy to create applications with artificial intelligence, simply by pasting the official documentation to any assistant and asking it to build it for you and, as if by magic, you'll have it working thanks to the fact that GenosDB is loaded integrated from the CDN. https://github.com/estebanrfp/gdb/wiki/GDB-API-Reference And here's a post from the author on how to build a distributed todolist app in real time.https://genosdb.com/build-a-to-do-list-in-minutes-with-genos...

This seems like an impressive amount of work and an interesting way to combine RBAC + [realtime] Sync/Conflict Resolution + [local] Document Storage/Querying (and I'm personally interested in the geo module and am intrigued by the AI module to help with some async data pipelines); however, I'm having trouble seeing how this is graph database? Maybe I'm misunderstanding, but I don't see ways for traversing the graph. I understand that you can create and store a node and then link that node to another node, but how could I query for nodes based on that link/relationship? E.g., ``` const alice = await db.put({ name: "Alice", age: 30 }); const bob = await db.put({ name: "Bob", age: 31 }); const cooper = await db.put({ name: "Cooper", age: 29 }); const dwight = await db.put({ name: "Dwight", age: 33 }); await db.link(alice, bob);