GenosDB: Distributed Graph Database with Module Support

genosdb.com

3 points·estebanrfp··4 comments

A lightweight, decentralized graph database designed for modern web applications, offering real-time peer-to-peer synchronization, WebAuthn-based authentication, role-based access control (RBAC), and efficient local storage utilizing OPFS.

Looks promising! Excellent!

Compared to TigerGraph, Neo4j, JanusGraph, Dgraph, and ArangoDB, I’d love to see a benchmark-ish comparison of GenosDB in terms of performance, latency, scalability, modularity, and flexibility.

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

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://github.com/estebanrfp/gdb Package: https://www.npmjs.com/package/genosdb Docs: https://genosdb.com

Open to micro-benchmarking if there’s community interest.

Reply on news.ycombinator.com