f5c0455af4
Summary: What's done: - `RecordAccessor` can represent remote data - `GraphDbAccessor` manages remote data - Cleanup: different `EdgeAccessor lazyness (@dgleich: take a look), unused methods, documentation... - `TODO` placeholders for remote implementation What's not done: - RPC and data transfer - how exactly remote errors are handled - not sure if any MVCC Record info for remote data should be tracked - WAL and RPC Deltas properly handled (Gleich working on extracting `Wal::Op`) This implementation should not break single-node execution, and should provide good abstractions and placeholders for distributed. Once that's satisfied, it should land. Reviewers: dgleich, buda, mislav.bradac Reviewed By: dgleich Subscribers: dgleich, pullbot Differential Revision: https://phabricator.memgraph.io/D1030
memgraph
Memgraph is an ACID compliant high performance transactional distributed in-memory graph database featuring runtime native query compiling, lock free data structures, multi-version concurrency control and asynchronous IO.
dependencies
Memgraph can be compiled using any modern c++ compiler. It mostly relies on the standard template library, however, some things do require external libraries.
Some code contains linux-specific libraries and the build is only supported on a 64 bit linux kernel.
- linux
- clang 3.8 (good c++11 support, especially lock free atomics)
- antlr (compiler frontend)
- cppitertools
- fmt format
- google benchmark
- google test
- glog
- gflags