Need advice about which tool to choose?Ask the StackShare community!

Graph Engine

4
29
+ 1
1
RedisGraph

31
107
+ 1
7
Add tool

Graph Engine vs RedisGraph: What are the differences?

Introduction:

Graph Engine and RedisGraph are both graph database management systems that provide efficient graph processing capabilities. However, there are key differences between the two that differentiate them in terms of performance, scalability, and features.

1. Query Language: Graph Engine uses the Language-Integrated Knowledge Query (LIKQ) language for querying, which integrates with C# and provides advanced functionalities for graph traversal. In contrast, RedisGraph uses a Cypher-like query language inspired by Neo4j, making it easier for developers familiar with Cypher to transition and query data.

2. Storage Model: Graph Engine uses a vertex-centric storage model, enabling efficient graph traversal by storing edges as attributes of vertices. On the other hand, RedisGraph adopts a property graph model, which stores nodes and relationships as first-class citizens, allowing for complex graph structures and properties to be represented in the database.

3. Replication and Sharding: RedisGraph supports replication and sharding out of the box, allowing for horizontal scaling and high availability in distributed environments. In comparison, Graph Engine does not have built-in support for replication and sharding, potentially limiting its scalability in large-scale deployments.

4. In-memory Processing: Graph Engine excels in in-memory graph processing, utilizing memory efficiently for real-time analytics and pattern matching. RedisGraph also leverages in-memory processing but provides disk persistence for durability, ensuring data integrity and fault tolerance in case of failures.

5. Community Support: RedisGraph is developed and maintained by Redis Labs, a well-established company in the database industry, ensuring ongoing support, updates, and documentation. Graph Engine, while supported by Microsoft Research, has a smaller community and may have limited resources for user assistance and development.

6. Ecosystem Integration: RedisGraph seamlessly integrates with the broader Redis ecosystem, allowing users to leverage other Redis modules and features, such as caching, pub/sub messaging, and transactions. Graph Engine, while compatible with Azure services and Microsoft products, may have less integration with third-party tools and technologies, limiting its interoperability in diverse software environments.

In Summary, Graph Engine and RedisGraph differ in query language, storage model, replication/sharding capabilities, in-memory processing, community support, and ecosystem integration, each catering to specific use cases and preferences in graph database management.

Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Graph Engine
Pros of RedisGraph
  • 1
    Flexiable, very expressive, native C# works
  • 3
    10x – 600x faster than any other graph database
  • 2
    Cypher – graph query language
  • 1
    Great graphdb
  • 1
    Open source

Sign up to add or upvote prosMake informed product decisions

- No public GitHub repository available -

What is Graph Engine?

The distributed RAM store provides a globally addressable high-performance key-value store over a cluster of machines. Through the RAM store, GE enables the fast random data access power over a large distributed data set.

What is RedisGraph?

RedisGraph is a graph database developed from scratch on top of Redis, using the new Redis Modules API to extend Redis with new commands and capabilities. Its main features include: - Simple, fast indexing and querying - Data stored in RAM, using memory-efficient custom data structures - On disk persistence - Tabular result sets - Simple and popular graph query language (Cypher) - Data Filtering, Aggregation and ordering

Need advice about which tool to choose?Ask the StackShare community!

What companies use Graph Engine?
What companies use RedisGraph?
See which teams inside your own company are using Graph Engine or RedisGraph.
Sign up for StackShare EnterpriseLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Graph Engine?
What tools integrate with RedisGraph?
    No integrations found
    What are some alternatives to Graph Engine and RedisGraph?
    Neo4j
    Neo4j stores data in nodes connected by directed, typed relationships with properties on both, also known as a Property Graph. It is a high performance graph store with all the features expected of a mature and robust database, like a friendly query language and ACID transactions.
    Dgraph
    Dgraph's goal is to provide Google production level scale and throughput, with low enough latency to be serving real time user queries, over terabytes of structured data. Dgraph supports GraphQL-like query syntax, and responds in JSON and Protocol Buffers over GRPC and HTTP.
    JanusGraph
    It is a scalable graph database optimized for storing and querying graphs containing hundreds of billions of vertices and edges distributed across a multi-machine cluster. It is a transactional database that can support thousands of concurrent users executing complex graph traversals in real time.
    Titan
    Titan is a scalable graph database optimized for storing and querying graphs containing hundreds of billions of vertices and edges distributed across a multi-machine cluster. Titan is a transactional database that can support thousands of concurrent users executing complex graph traversals in real time.
    Cayley
    Cayley is an open-source graph inspired by the graph database behind Freebase and Google's Knowledge Graph. Its goal is to be a part of the developer's toolbox where Linked Data and graph-shaped data (semantic webs, social networks, etc) in general are concerned.
    See all alternatives