X-Git-Url: http://www2.svjatoslav.eu/gitweb/?a=blobdiff_plain;f=doc%2Findex.html;h=34a8cc164340f6dd4a7695c57474d1a408ef49cd;hb=d8fc769e32de3c36ee37ad7ca0450c4c0e05a765;hp=28f924f76fc0583f20e9a4a859579d8fe4f49dcf;hpb=bb7b2daf4049f53eefbde9912daca7f31a3b6717;p=sixth-data.git

diff --git a/doc/index.html b/doc/index.html
index 28f924f..34a8cc1 100644
--- a/doc/index.html
+++ b/doc/index.html
@@ -2,12 +2,12 @@
 <html lang="en">
 <head>
 <title>Sixth - system for data storage, computation, exploration and interaction</title>
-<!-- 2017-06-13 Tue 22:14 -->
+<!-- 2017-11-29 Wed 23:57 -->
 <meta charset="utf-8">
 <meta name="viewport" content="width=device-width, initial-scale=1">
 <meta name="generator" content="Org-mode">
 <meta name="author" content="Svjatoslav Agejenko">
-<link href="https://bootswatch.com/darkly/bootstrap.min.css" rel="stylesheet">
+<link href="https://bootswatch.com/4/darkly/bootstrap.min.css" rel="stylesheet">
 <script src="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.11.2/jquery.min.js"></script>
 <script src="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.1/js/bootstrap.min.js"></script>"
 <style type="text/css">
@@ -220,29 +220,36 @@ License</a> or later as published by the Free Software Foundation.
 </ul>
 </li>
 
-<li><a href="http://svjatoslav.eu/programs.jsp">other applications hosted at svjatoslav.eu</a>
+<li><a href="http://www.svjatoslav.eu/programs.jsp">other applications hosted at svjatoslav.eu</a>
 </li>
 </ul>
 
 
 <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.
 </li>
+
+<li>Eliminate constant moving and converting of data between 2 systems
+and make computing happen close to where the data is stored.
+</li>
+
 <li>Abstract away difference between RAM VS persistent storage. Let
 the system decide at runtime which data to keep in what kind of
 memory.
@@ -251,10 +258,11 @@ memory.
 </li>
 </ul>
 </div>
+</div>
 
-<div id="outline-container-sec-1-1" class="outline-3">
-<h3 id="sec-1-1"><span class="section-number-3">1.1</span> Inspiration</h3>
-<div class="outline-text-3" id="text-1-1">
+<div id="outline-container-sec-2" class="outline-2">
+<h2 id="sec-2"><span class="section-number-2">2</span> Inspiration</h2>
+<div class="outline-text-2" id="text-2">
 <ul class="org-ul">
 <li>Relational databases:
 <ul class="org-ul">
@@ -274,126 +282,257 @@ memory.
 <li>Transparent cansistency, checksumming and deduplication.
 </li>
 <li>(Git as a database:
+</li>
+</ul>
+<p>
 <a href="https://www.kenneth-truyers.net/2016/10/13/git-nosql-database/">https://www.kenneth-truyers.net/2016/10/13/git-nosql-database/</a> )
+</p>
+</li>
+</ul>
+</div>
+
+<div id="outline-container-sec-2-1" class="outline-3">
+<h3 id="sec-2-1"><a id="ID-d2375acc-af14-4f18-8ad0-7949501178c5" name="ID-d2375acc-af14-4f18-8ad0-7949501178c5"></a><span class="section-number-3">2.1</span> Brain</h3>
+<div class="outline-text-3" id="text-2-1">
+<ul class="org-ul">
+<li>Appears to have more than 3D dimensional design. Food for
+thought&#x2026;)
+<ul class="org-ul">
+<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>
+</li>
+</ul>
+</li>
+
+<li>It directly inspires following ideas
+<ul class="org-ul">
+<li><a href="#sec-3-1">Distributed comutation and data storage</a>
+</li>
+<li><a href="#sec-3-2">Mapping of hyperspace to traditional object-oriented model</a>
+</li>
+<li><a href="#sec-3-3">Handling of relations</a>
 </li>
 </ul>
 </li>
 </ul>
 </div>
 </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">
+<div id="outline-container-sec-3" class="outline-2">
+<h2 id="sec-3"><span class="section-number-2">3</span> Ideas</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"><a id="ID-5d287158-53ea-44a2-a754-dd862366066a" name="ID-5d287158-53ea-44a2-a754-dd862366066a"></a><span class="section-number-3">3.1</span> Distributed computation and data storage</h3>
+<div class="outline-text-3" id="text-3-1">
 <p>
-I see 4D data structure.
+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.
 </p>
-
-
-<figure>
-<p><img src="data model.png" class="img-responsive" alt="data model.png">
+</div>
+</div>
+<div id="outline-container-sec-3-2" class="outline-3">
+<h3 id="sec-3-2"><a id="ID-a117c11e-97c1-4822-88b2-9fc10f96caec" name="ID-a117c11e-97c1-4822-88b2-9fc10f96caec"></a><span class="section-number-3">3.2</span> Mapping of hyperspace to traditional object-oriented model</h3>
+<div class="outline-text-3" id="text-3-2">
+<p>
+Object oriented programming is inspired by the way human mind
+operates. It allows programmer to express ideas to computer in a more
+human-like terms.
 </p>
-</figure>
 
 <p>
-Dimensions:
+It is possible to map object model to geometrical hyperspace:
 </p>
+
 <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>Object is a point in space (universe). Each object member variable
+translates to its own dimension. That is: if class declares 4
+variables for an object, then corresponding object can be stored as
+a single point inside 4 dimensional space. Variable values translate
+to point coordinates in space. That is: Integer, floating point
+number and even boolean and string can be translated to linear value
+that can be used as a coordinate along particular dimension.
 </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>Each class declares its own space (universe). All class instances
+(objects) are points inside that particular universe. References
+between objects of different types are hyperlinks (portals) between
+different universes.
 </li>
 </ul>
-
+</div>
+</div>
+<div id="outline-container-sec-3-3" class="outline-3">
+<h3 id="sec-3-3"><a id="ID-b6b15bd2-c78b-4c51-a343-72843a515c29" name="ID-b6b15bd2-c78b-4c51-a343-72843a515c29"></a><span class="section-number-3">3.3</span> Handling of relations</h3>
+<div class="outline-text-3" id="text-3-3">
 <p>
-Partitioning/clustering:
+Consider we want to create database of books and authors. Book can
+have multiple authors, and single person can be author for multiple
+books. It is possible to store how many hours of work each author has
+contributed to every book, using hyperspace as follows:
 </p>
+
+<ul class="org-ul">
+<li>Every dimension corresponds to one particular book author. (10
+authors in the database, would require 10 dimensional space)
+<ul class="org-ul">
+<li>Point in space corresponds to one particular book.
 <ul class="org-ul">
-<li>Why not to partition/(load balance) as required across networked
-physical computers along arbitrary dimension(s) declared above ?
+<li>Point location along particular (author) dimension corresponds
+to amount of work contributed by particular author for given
+book.
+</li>
+</ul>
 </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:
+Alternatively:
 </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>Every dimension corresponds to one particular book.
+<ul class="org-ul">
+<li>Point in space corresponds to one particular author in the entire
+database.
+<ul class="org-ul">
+<li>Point location along particular (book) dimension corresponds to
+amount of work contributed for book by given author (point).
 </li>
-<li>Once featres are locked. Anything can be optimised. Optimization for
-size (deduplication) can be solved using Git style content
-addressible storage mechanism.
+</ul>
 </li>
 </ul>
+</li>
+</ul>
+</div>
 </div>
+
+<div id="outline-container-sec-3-4" class="outline-3">
+<h3 id="sec-3-4"><span class="section-number-3">3.4</span> Layered architecture</h3>
+<div class="outline-text-3" id="text-3-4">
+<dl class="org-dl">
+<dt> layer 1 </dt><dd>disk / block storage / partition
+</dd>
+
+<dt> layer 2 </dt><dd>key/value storage. Keys are unique and are dictated by
+storage engine. Value is arbitrary but limited size byte
+array. This layer is responsible for handling disk
+defragmentation and consistency in case of crash
+recovery.
+</dd>
+
+<dt> layer 3 </dt><dd>key/value storage. Keys are content hashes. Values are
+arbitrary but limited size content byte arrays. This
+layer effectively implements content addressable
+storage. Content addressible storage enables GIT-like
+behavior (possibility for competing branches, retaining
+history, transparent deduplication)
+</dd>
+
+<dt> layer 4 </dt><dd>Implements arbitrary dimensional multiverse.
+</dd>
+
+<dt> layer 5 </dt><dd>Distributed computation engine.
+</dd>
+</dl>
 </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">
+</div>
+
+<div id="outline-container-sec-4" class="outline-2">
+<h2 id="sec-4"><span class="section-number-2">4</span> Current status</h2>
+<div class="outline-text-2" id="text-4">
 <ul class="org-ul">
+<li>More or less defined <a href="#sec-1">Vision / goal</a>.
+</li>
+
+<li>Collected some <a href="#sec-2-1">ideas</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>
+</div>
+</div>
 
+<div id="outline-container-sec-5" class="outline-2">
+<h2 id="sec-5"><span class="section-number-2">5</span> See also</h2>
+<div class="outline-text-2" id="text-5">
 <p>
-Long term goal is to implement more advanced features on top of this.
+Interesting or competing projects with good ideas:
 </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>GRAKN.AI: database in the form of a knowledge graph that uses
+machine reasoning to simplify data processing challenges for AI
+applications.
+<ul class="org-ul">
+<li><a href="https://grakn.ai/">https://grakn.ai/</a>
+</li>
+</ul>
+</li>
+
+<li>Gemstone/S based on Smalltalk.
+<ul class="org-ul">
+<li><a href="http://esug.org/data/ESUG2015/3%20wednesday/1100-1130%20SQL%20Queries%20on%20Smalltalk%20Objects/SQL%20Queries%20in%20Smalltalk%20(James%20Foster)">http://esug.org/data/ESUG2015/3%20wednesday/1100-1130%20SQL%20Queries%20on%20Smalltalk%20Objects/SQL%20Queries%20in%20Smalltalk%20(James%20Foster)</a>.pdf
+</li>
+</ul>
+</li>
+
+<li>Magma distributed database in Smalltalk.
 <ul class="org-ul">
 <li><a href="http://wiki.squeak.org/squeak/2665">http://wiki.squeak.org/squeak/2665</a>
 </li>
 </ul>
-</div>
+</li>
+
+<li>ZetaVM
+<ul class="org-ul">
+<li><a href="https://github.com/zetavm/zetavm">https://github.com/zetavm/zetavm</a>
+</li>
+</ul>
+</li>
+</ul>
 </div>
 </div>
 </div><div class="col-md-3"><nav id="table-of-contents">
 <div id="text-table-of-contents" class="bs-docs-sidebar">
 <ul class="nav">
-<li><a href="#sec-1">1. Vision / goal</a>
+<li><a href="#sec-1">1. Vision / goal</a></li>
+<li><a href="#sec-2">2. Inspiration</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>
+<li><a href="#sec-2-1">2.1. Brain</a></li>
 </ul>
 </li>
-<li><a href="#sec-2">2. Current status</a></li>
-<li><a href="#sec-3">3. </a>
+<li><a href="#sec-3">3. Ideas</a>
 <ul class="nav">
-<li><a href="#sec-3-1">3.1. check out Magma</a></li>
+<li><a href="#sec-3-1">3.1. Distributed computation and data storage</a></li>
+<li><a href="#sec-3-2">3.2. Mapping of hyperspace to traditional object-oriented model</a></li>
+<li><a href="#sec-3-3">3.3. Handling of relations</a></li>
+<li><a href="#sec-3-4">3.4. Layered architecture</a></li>
 </ul>
 </li>
+<li><a href="#sec-4">4. Current status</a></li>
+<li><a href="#sec-5">5. See also</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-11-29 Wed 23:57</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>
