runtime objects for every transaction. How about creating united
database/computation engine instead to:
- + Eliminate constant moving and converting of data between 2 systems
- and make computing happen close to where the data is stored.
+ + Eliminate constant moving and converting of data between 2 systems
+ and make computing happen close to where the data is stored.
- + Abstract away difference between RAM VS persistent storage. Let
- the system decide at runtime which data to keep in what kind of
- memory.
+ + Abstract away difference between RAM VS persistent storage. Let
+ the system decide at runtime which data to keep in what kind of
+ memory.
* Inspiration
+ Relational databases:
efficiently simulate arbitrary dimensional network topology between
computational units. So that when we are solving/simulating for
example 5 dimensional problem, we can arrange computational units
- into virtual 5D network.
+ into virtual 5D network. See:
+ http://www.mission-base.com/tamiko/theory/cm_txts/di-ch2.html
* Ideas
** Geometrical computation
+ [[id:01aa65c1-3d44-44a8-9b90-58454bc6be80][CM-1 Connection Machine]]
++ http://phantomos.org/
+ + Programs run forever. System crash or reboot does not destroy
+ state of running program.
+
++ Taichi: A Language for High-Performance Computation onSpatially
+ Sparse Data Structures
+ + http://taichi.graphics/wp-content/uploads/2019/09/taichi_lang.pdf
+
+ GRAKN.AI
+ database in the form of a knowledge graph that uses machine
reasoning to simplify data processing challenges for AI