ArcadeDB vs. OrigoDB vs. RecallGraph vs. python-sql Comparison Chart

Manage complex models using ArcadeDB without any compromise. Forget about Polyglot Persistence. no need for multiple databases. You can store graphs, documents, key values and time series all in one ArcadeDB Multi-Model database. Since each model is native to the database engine, you don't have to worry about translations slowing you down. ArcadeDB's engine was built with Alien Technology. It's able to crunch millions of records per second. With ArcadeDB, the traversing speed is not affected by the database size. It is always constant, whether your database has a few records or billions. ArcadeDB can work as an embedded database, on a single server and can scale up using multiple servers with Kubernetes. Flexible enough to run on any platform with a small footprint. Your data is secure. Our unbreakable fully transactional engine assures durability for mission-critical production databases. ArcadeDB uses a Raft Consensus Algorithm to maintain consistency across multiple servers.

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.