tursom/memgraph
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
abedfb29b1
memgraph/experimental/distributed
History
Goran Zuzic abedfb29b1 Make Distributed Singleton (and remove unused code) 
Reviewers: sasa.stanko, buda

Reviewed By: sasa.stanko

Differential Revision: https://phabricator.memgraph.io/D694
2017-08-22 17:14:54 +02:00
..
src Make Distributed Singleton (and remove unused code) 2017-08-22 17:14:54 +02:00
tests Make Distributed Singleton (and remove unused code) 2017-08-22 17:14:54 +02:00
.clang-format Merged experimental repo. 2017-08-03 12:48:19 +02:00
.gitignore Merged experimental repo. 2017-08-03 12:48:19 +02:00
CMakeLists.txt Make System a singleton + Fix some protocol errors 2017-08-22 16:30:25 +02:00
init Merged experimental repo. 2017-08-03 12:48:19 +02:00
README.md Make System a singleton + Fix some protocol errors 2017-08-22 16:30:25 +02:00

README.md

distributed memgraph

This subdirectory structure implements distributed infrastructure of Memgraph.

terminology

  • Memgraph Node Id (mnid): a machine (processs) that runs a (distributed) Memgraph program.
  • Node: a computer that performs (distributed) work.
  • Vertex: an abstract graph concept.
  • Reactor: a unit of concurrent execution, lives on its own thread.
  • Connector: a (one-way) communication abstraction between Reactors. The reactors can be on the same machine or on different processes.
  • EventStream: read-end of a connector, is owned by exactly one Reactor/thread.
  • Channel: write-end of a connector, can be owned (wrote into) by multiple threads.

conventions

  1. Locked: A method having a Locked... prefix indicates that you have to lock the appropriate mutex before calling this function.

dependencies

  • cereal