I have been wondering how Giraph can support a large graph that is constantly
being updated by multiple jobs running simultaneously.
Output of jobs are continually adding extra and modifying edges / vertices
in the graph. Some notion of transactional concurrency would be needed as well
in this environment.
>From what I can see it appears that Giraph may be well suited to working with
>snapshots of such as system rather than the root implementation, but I feel
>that I might be missing a core design pattern.