1 follower
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.
A temporal database is one that gives you access to historical data, i.e., old data which would've otherwise been overwritten by new data, e.g. during...
Point-in-time, range-based and more... · At the time of writing this post, all of RecallGraph's API endpoints are designed to serve a particular type of...
For single/bulk writes · Quick reference For single document writes (create/update/replace/delete) - YES. For bulk document writes...
Which one does RecallGraph belong to? · Another question I often get: "How does RecallGraph stack up against AWS Timestream (or some other time-series...
GraphQL, Gremlin, AQL, Cypher, etc. · If the query language in question supports arbitrary traversal depths and temporal clauses, then it could,...
A question I've been asked more than once on ArangoDB's community forums and elsewhere: "Is RecallGraph supposed to be used for versioning document...