<html lang="en">
<head>
<title>Sixth - system for data storage, computation, exploration and interaction</title>
-<!-- 2017-06-13 Tue 22:14 -->
+<!-- 2017-07-02 Sun 22:49 -->
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<meta name="generator" content="Org-mode">
<div id="outline-container-sec-1" class="outline-2">
-<h2 id="sec-1"><span class="section-number-2">1</span> Vision / goal</h2>
+<h2 id="sec-1"><a id="ID-f6764282-a6f6-44e6-8716-b428074dd093" name="ID-f6764282-a6f6-44e6-8716-b428074dd093"></a><span class="section-number-2">1</span> Vision / goal</h2>
<div class="outline-text-2" id="text-1">
<p>
-Provide versioned, clustered, flexible, object-relational database
-
functionality for the <a href="http://www2.svjatoslav.eu/gitbrowse/sixth/doc/index.html">Sixth computation engine</a>.
+Provide versioned, clustered, flexible, distributed, multi-dimensional
+
data storage engine for the <a href="http://www2.svjatoslav.eu/gitbrowse/sixth/doc/index.html">Sixth computation engine</a>.
</p>
+<ul class="org-ul">
+<li>Speaking of traditional relational database and object oriented
+business applications:
<ul class="org-ul">
<li>I hate object-relational impedance mismatch.
</li>
-<li>I don't like to convert data between persistent database and runtime
-objects for every transaction. How about creating united
+<li>I don't like to convert data between persistent database and
+runtime objects for every transaction. How about creating united
database/computation engine instead to:
<ul class="org-ul">
<li>Eliminate constant moving and converting of data between 2 systems.
</ul>
</li>
</ul>
+</li>
+</ul>
</div>
<div id="outline-container-sec-1-1" class="outline-3">
</li>
</ul>
</li>
-</ul>
-</div>
-</div>
-
-<div id="outline-container-sec-1-2" class="outline-3">
-<h3 id="sec-1-2"><span class="section-number-3">1.2</span> Solution (the big idea)</h3>
-<div class="outline-text-3" id="text-1-2">
-<p>
-I see 4D data structure.
-</p>
-
-
-<figure>
-<p><img src="data model.png" class="img-responsive" alt="data model.png">
-</p>
-</figure>
-<p>
-Dimensions:
-</p>
+<li>Brain (appears to have more than 3D dimensional design. Food for
+thought…)
<ul class="org-ul">
-<li>List of all the objecs in the system (rows).
-</li>
-<li>List of all declared unique object fields (columns).
-</li>
-<li>List of all historical transactions/commits/versions (think of
-sheets of paper).
-</li>
-<li>List of all concurrently running branches/threads. Branches can
-appear and merge over time as needed.
-</li>
-<li>(Every cell is concrete field value within an object)
-</li>
-</ul>
-
-<p>
-Partitioning/clustering:
-</p>
+<li><a href="https://singularityhub.com/2017/06/21/is-there-a-multidimensional-mathematical-world-hidden-in-the-brains-computation/">https://singularityhub.com/2017/06/21/is-there-a-multidimensional-mathematical-world-hidden-in-the-brains-computation/</a>
<ul class="org-ul">
-<li>Why not to partition/(load balance) as required across networked
-physical computers along arbitrary dimension(s) declared above ?
+<li>From there comes following idea: Maybe every problem can be
+translated to geometry (use any shapes and as many dimensions as
+you need). Solution(s) to such problems would then appear as
+relatively simple search/comparison/lookup results. As a bonus,
+such geometrical *data storage* AND *computation* can be
+naturally made in *parallel* and *distributed*. That's what
+neurons in the brain appear to be doing ! :) . Learning means
+building/updating the model (the hard part). Question answering
+is making (relatively simple) lookups (geometrical queries)
+against the model.
</li>
</ul>
-
-<p>
-Indexing (for fast searching):
-</p>
-<ul class="org-ul">
-<li>Why not to index along arbitrary dimensions (as required) ?
</li>
</ul>
-
-<p>
-Further optimizations:
-</p>
-<ul class="org-ul">
-<li>In current early stage, trying to focus on minimum possible set of
-features that would provide maximum possible set of power/benefit :)
-</li>
-<li>Once featres are locked. Anything can be optimised. Optimization for
-size (deduplication) can be solved using Git style content
-addressible storage mechanism.
</li>
</ul>
</div>
</div>
</div>
+
<div id="outline-container-sec-2" class="outline-2">
<h2 id="sec-2"><span class="section-number-2">2</span> Current status</h2>
<div class="outline-text-2" id="text-2">
<ul class="org-ul">
+<li>More or less defined <a href="#sec-1">Vision / goal</a>.
+</li>
+
<li>Implemented very simple persistent key-value map.
+<ul class="org-ul">
+<li>Long term goal is to use it as a backing storage engine and
+implement more advanced features on top of this.
+</li>
+</ul>
</li>
</ul>
-
-<p>
-Long term goal is to implement more advanced features on top of this.
-</p>
</div>
</div>
<div id="outline-container-sec-3" class="outline-2">
<h2 id="sec-3"><span class="section-number-2">3</span> <span class="label label-primary TODO">TODO</span> </h2>
<div class="outline-text-2" id="text-3">
-</div><div id="outline-container-sec-3-1" class="outline-3">
-<h3 id="sec-3-1"><span class="section-number-3">3.1</span> check out Magma</h3>
-<div class="outline-text-3" id="text-3-1">
+<ul class="org-ul">
+<li>check out Magma
<ul class="org-ul">
<li><a href="http://wiki.squeak.org/squeak/2665">http://wiki.squeak.org/squeak/2665</a>
</li>
</ul>
-</div>
+</li>
+</ul>
</div>
</div>
</div><div class="col-md-3"><nav id="table-of-contents">
<li><a href="#sec-1">1. Vision / goal</a>
<ul class="nav">
<li><a href="#sec-1-1">1.1. Inspiration</a></li>
-<li><a href="#sec-1-2">1.2. Solution (the big idea)</a></li>
</ul>
</li>
<li><a href="#sec-2">2. Current status</a></li>
-<li><a href="#sec-3">3. </a>
-<ul class="nav">
-<li><a href="#sec-3-1">3.1. check out Magma</a></li>
-</ul>
-</li>
+<li><a href="#sec-3">3. </a></li>
</ul>
</div>
</nav>
</div></div></div>
<footer id="postamble" class="">
<div><p class="author">Author: Svjatoslav Agejenko</p>
-<p class="date">Created: 2017-06-13 Tue 22:14</p>
+<p class="date">Created: 2017-07-02 Sun 22:49</p>
<p class="creator"><a href="http://www.gnu.org/software/emacs/">Emacs</a> 25.1.1 (<a href="http://orgmode.org">Org-mode</a> 8.2.10)</p>
</div>
</footer>
#+HTML_HEAD: </style>
* Vision / goal
-Provide versioned, clustered, flexible, object-relational database
-functionality for the [[http://www2.svjatoslav.eu/gitbrowse/sixth/doc/index.html][Sixth computation engine]].
-
-+ I hate object-relational impedance mismatch.
-
-+ I don't like to convert data between persistent database and runtime
- objects for every transaction. How about creating united
- database/computation engine instead to:
- + Eliminate constant moving and converting of data between 2 systems.
- + Abstract away difference between RAM VS persistent storage. Let
- the system decide at runtime which data to keep in what kind of
- memory.
+ :PROPERTIES:
+ :ID: f6764282-a6f6-44e6-8716-b428074dd093
+ :END:
+Provide versioned, clustered, flexible, distributed, multi-dimensional
+data storage engine for the [[http://www2.svjatoslav.eu/gitbrowse/sixth/doc/index.html][Sixth computation engine]].
+
++ Speaking of traditional relational database and object oriented
+ business applications:
+ + I hate object-relational impedance mismatch.
+
+ + I don't like to convert data between persistent database and
+ runtime objects for every transaction. How about creating united
+ database/computation engine instead to:
+ + Eliminate constant moving and converting of data between 2 systems.
+ + 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:
+ (Git as a database:
https://www.kenneth-truyers.net/2016/10/13/git-nosql-database/ )
-** Solution (the big idea)
-I see 4D data structure.
-
-[[file:data model.png]]
-
-Dimensions:
-+ List of all the objecs in the system (rows).
-+ List of all declared unique object fields (columns).
-+ List of all historical transactions/commits/versions (think of
- sheets of paper).
-+ List of all concurrently running branches/threads. Branches can
- appear and merge over time as needed.
-+ (Every cell is concrete field value within an object)
-
-Partitioning/clustering:
-+ Why not to partition/(load balance) as required across networked
- physical computers along arbitrary dimension(s) declared above ?
-
-Indexing (for fast searching):
-+ Why not to index along arbitrary dimensions (as required) ?
-
-Further optimizations:
-+ In current early stage, trying to focus on minimum possible set of
- features that would provide maximum possible set of power/benefit :)
-+ Once featres are locked. Anything can be optimised. Optimization for
- size (deduplication) can be solved using Git style content
- addressible storage mechanism.
++ Brain (appears to have more than 3D dimensional design. Food for
+ thought...)
+ + https://singularityhub.com/2017/06/21/is-there-a-multidimensional-mathematical-world-hidden-in-the-brains-computation/
+ + From there comes following idea: Maybe every problem can be
+ translated to geometry (use any shapes and as many dimensions as
+ you need). Solution(s) to such problems would then appear as
+ relatively simple search/comparison/lookup results. As a bonus,
+ such geometrical *data storage* AND *computation* can be
+ naturally made in *parallel* and *distributed*. That's what
+ neurons in the brain appear to be doing ! :) . Learning means
+ building/updating the model (the hard part). Question answering
+ is making (relatively simple) lookups (geometrical queries)
+ against the model.
+
* Current status
-- Implemented very simple persistent key-value map.
+- More or less defined [[id:f6764282-a6f6-44e6-8716-b428074dd093][Vision / goal]].
-Long term goal is to implement more advanced features on top of this.
+- Implemented very simple persistent key-value map.
+ - Long term goal is to use it as a backing storage engine and
+ implement more advanced features on top of this.
* TODO
-** check out Magma
++ check out Magma
+ http://wiki.squeak.org/squeak/2665
projects / sixth-data.git / commitdiff
