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

diff --git a/doc/index.html b/doc/index.html
index d0f979d..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-07-19 Wed 21:46 -->
+<!-- 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">
@@ -236,6 +236,7 @@ data storage engine for the <a href="http://www2.svjatoslav.eu/gitbrowse/sixth/d
 <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>
@@ -243,9 +244,12 @@ business applications:
 <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.
@@ -253,8 +257,6 @@ memory.
 </ul>
 </li>
 </ul>
-</li>
-</ul>
 </div>
 </div>
 
@@ -280,9 +282,11 @@ memory.
 <li>Transparent cansistency, checksumming and deduplication.
 </li>
 <li>(Git as a database:
-<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> )
 </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>
@@ -299,36 +303,108 @@ thought&#x2026;)
 </ul>
 </li>
 
-<li>From there come following ideas:
+<li>It directly inspires following ideas
 <ul class="org-ul">
-<li>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>
-
-<li>Mapping of hyperspace to traditional object-oriented programming
-model:
+<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-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>
+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>
+</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>
+
+<p>
+It is possible to map object model to geometrical hyperspace:
+</p>
+
 <ul class="org-ul">
-<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>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>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>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>
+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>Point location along particular (author) dimension corresponds
+to amount of work contributed by particular author for given
+book.
+</li>
+</ul>
+</li>
+</ul>
+</li>
+</ul>
+
+<p>
+Alternatively:
+</p>
+
+<ul class="org-ul">
+<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>
 </ul>
 </li>
@@ -337,11 +413,42 @@ hyperlinks (portals) between different universes.
 </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>
 
-<div id="outline-container-sec-3" class="outline-2">
-<h2 id="sec-3"><span class="section-number-2">3</span> Current status</h2>
-<div class="outline-text-2" id="text-3">
+<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>
@@ -360,9 +467,9 @@ implement more advanced features on top of this.
 </div>
 </div>
 
-<div id="outline-container-sec-4" class="outline-2">
-<h2 id="sec-4"><span class="section-number-2">4</span> See also</h2>
-<div class="outline-text-2" id="text-4">
+<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>
 Interesting or competing projects with good ideas:
 </p>
@@ -390,6 +497,13 @@ applications.
 </li>
 </ul>
 </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>
@@ -402,15 +516,23 @@ applications.
 <li><a href="#sec-2-1">2.1. Brain</a></li>
 </ul>
 </li>
-<li><a href="#sec-3">3. Current status</a></li>
-<li><a href="#sec-4">4. See also</a></li>
+<li><a href="#sec-3">3. Ideas</a>
+<ul class="nav">
+<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-07-19 Wed 21:46</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>
