Graph Database

[CMCDragonkai]

The convergence between Emergence configuration, Relay network and Architect expressions and Polykey is a distributed graph database.

We need to examine:

• Incremental Graph Processing - https://github.com/janestreet/incremental
• Graph Rewrites - https://en.wikipedia.org/wiki/Graph_rewriting
• Operational Transformation - https://en.wikipedia.org/wiki/Operational_transformation
• CRDTs - https://en.wikipedia.org/wiki/Conflict-free_replicated_data_type
• LVars - https://github.com/iu-parfunc/lvars
• Indexing Graph/Hierarchical Data - a common way of doing this is taking your hierarchical structure and encoding it some other representation (it can be a lossy representation or isomorphic or augmented), and this representation provides a certain access/update pattern that is better in performance. In fact multiple representations of the same data may be used, and for each representation we call them an "index". The holy grail is a data structure that is also an index (or is naturally an index). When you use multiple indexes to represent the same data in multiple dimensions, you need a way to coordinate the updates from each index to other indexes. Basically updates mediated via 1 index must be consistent with other indexes that also representing this data. This can be complicated.

We need a graph database that supports sharding, replication, incremental processing, self adjusting computations, capable of reconfiguration due to operator demands (multi-player game) and also external world events. This step is to first make it work. Then we can make it fast according to our Prime project.

[CMCDragonkai]

https://github.com/MatrixAI/Relay/issues/21

[CMCDragonkai]

I have a feeling that studying how the web browser's DOM is implemented would be a good starting point as well. The DOM is basically a graph structure that is quite dynamic, supporting user-initiated updates and also updates from code. I'm interested in how the updates propagate changes to rendering.

• https://www.w3.org/DOM/
• https://stackoverflow.com/questions/45748837/tree-structures-in-webkit-chrome
• https://docs.python.org/3/library/xml.dom.html
• https://github.com/google/incremental-dom
• https://news.ycombinator.com/item?id=8175680
• https://www.html5rocks.com/en/tutorials/internals/howbrowserswork/

Add support for the DOM to your browser. Focus on W3C DOM Level 1 and Level 2 first, since pretty much all current browsers support those completely. Then look at Level 3 and Level 4. The DOM is extremely fundamental to web programming, and so if you're going to actually build a modern web browser, it's entire design has to take this into consideration. Since you are writing the browser in C# you may want to take into consideration how you could leverage the existing .NET object model to your advantage. https://stackoverflow.com/a/15515561/582917

The scene graph and layout engines of Mozilla Servo may be quite interesting as well. Computer rendering field has probably done a lot of work here to take graphs and turn into some human usable output. In this case pretty graphics!