Graph Engine vs. OrigoDB vs. RecallGraph vs. python-sql Comparison Chart

Graph Engine (GE) is a distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation 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. The capability of fast data exploration and distributed parallel computing makes GE a natural large graph processing platform. GE supports both low-latency online query processing and high-throughput offline analytics on billion-node large graphs. Schema does matter when we need to process data efficiently. Strongly-typed data modeling is crucial for compact data storage, fast data access, and clear data semantics. GE is good at managing billions of run-time objects of varied sizes. One byte counts as the number of objects goes large. GE provides fast memory allocation and reallocation with high memory ratios.

RecallGraph is a versioned-graph data store - it retains all changes that its data (vertices and edges) have gone through to reach their current state. It supports point-in-time graph traversals, letting the user query any past state of the graph just as easily as the present. RecallGraph is a potential fit for scenarios where data is best represented as a network of vertices and edges (i.e., a graph) having the following characteristics: 1. Both vertices and edges can hold properties in the form of attribute/value pairs (equivalent to JSON objects). 2. Documents (vertices/edges) mutate within their lifespan (both in their individual attributes/values and in their relations with each other). 3. Past states of documents are as important as their present, necessitating retention and queryability of their change history. Also see this blog post for an intro - https://blog.recallgraph.tech/never-lose-your-old-data-again.