A distributed, fast open-source graph database for large-scale data with horizontal scalability and high availability.
NebulaGraph is an open-source distributed graph database that handles large-scale data with millisecond latency. It is designed for fast graph analytics and horizontal scalability, solving the challenge of managing and querying interconnected data at enterprise scale. The database is widely used in applications like social networks, recommendation engines, and knowledge graphs.
Developers and data engineers building applications that require complex relationship analysis, such as social media platforms, recommendation systems, fraud detection, and AI-driven knowledge graphs.
Developers choose NebulaGraph for its combination of high performance, strong consistency via RAFT, and seamless horizontal scaling. Its OpenCypher compatibility lowers the learning curve, while its distributed architecture ensures reliability for mission-critical graph workloads.
A distributed, fast open-source graph database featuring horizontal scalability and high availability
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Easily scales out to accommodate growing data and query loads, as emphasized in the README's key features for handling large volumes.
Uses the RAFT protocol to guarantee reliable data replication, providing enterprise-grade reliability for mission-critical applications.
Supports a familiar graph query language, lowering the adoption barrier for developers experienced with Cypher from other graph databases.
Includes various analytics algorithms, enabling complex graph analysis without relying on external tools, as listed in the features.
Setting up the distributed system from source requires managing multiple components, as indicated by the detailed installation guides and separate service architecture.
While tools are available, the ecosystem is less mature than competitors like Neo4j, often necessitating custom integrations for broader use cases.
Past major releases (e.g., v1.x to v2.x) introduced data format and protocol incompatibilities, complicating migrations, as noted in the README's notice.