X-Git-Url: http://www2.svjatoslav.eu/gitweb/?p=sixth-data.git;a=blobdiff_plain;f=doc%2Findex.html;h=9b7529556aac3310ceb3089f9f1fb705e7df91a4;hp=6d728f39b315b3460a4d38cb92a00c84fd652516;hb=1c5ed72204c3c535b06b2215c50d54fbdb18ee98;hpb=cc82d9db5cc7b60aef85665ba14410c04f7177b0 diff --git a/doc/index.html b/doc/index.html index 6d728f3..9b75295 100644 --- a/doc/index.html +++ b/doc/index.html @@ -2,7 +2,7 @@ Sixth Data - Data storage and computing engine - + @@ -201,7 +201,8 @@ $(function() {

1 General

@@ -254,89 +252,54 @@ git clone https://www2.svjatoslav.eu/git/sixth-data.git

2 Vision / goal

-Provide versioned, clustered, flexible, distributed, multi-dimensional -data storage engine for the Sixth computation engine. +Provide hackable, versioned, optimized, distributed, geometrical, +arbitrary dimensional (hypercube based) data storage and computation +engine (as inspired by the brain) for general purpose visual computing +environment called Sixth.

- +

+Because Lisp is hackable self defined programmable programming +language it would be used to provide imperative programming support. +

-
-

3 Inspiration

+

3 Inspiration

-

3.1 Brain

@@ -349,60 +312,77 @@ with CM-1 Connection Machine design. https://en.wikipedia.org/wiki/Connection_Machine

- +

+ +

+we can pre-distribute data across computation units and perform +parallel geometrical computation. +

-

4 Ideas

+

4 Reasons for hypercube as a so called first class citizen

-
-

4.1 Geometrical computation

-
    -
  • Inspired by Brain. +
  • Hypercube is quite general purpose data structure that naturally +encapsulates wide variety data and problems.
    • -
  • Wits nicely with CM-1 Connection Machine properties. + +
  • Nicely captures apparent properties of the brain. +
    • + +
  • Naturally supports distributed and parallel geometrical data storage +and computation. +
    • + +
  • Dedicated hardware like CM-1 can be built around hypercube concept +that results in data, computation process and hardware, all +beautifully fitting together while complementing each other +strengths. +
    • + +
  • Hypercube stored data (and computation process) has geometry by its +nature and should fit nicely with "3D first" user interface ideology +of the parent Sixth project.
+
+
+

5 Geometrical computation idea

+
+
+
+

5.1 Distributed computation and data storage

+
+

+Lots of problems can be translated to geometry (use any shapes and as +many dimensions as you need). Solution(s) to such problems could be +then found via geometrical search/comparison/lookup results. As a +bonus, such geometrical *data storage* AND *computation* can be +naturally made in *parallel* and *distributed*. +

-
-

4.1.1 Distributed computation and data storage

-

-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. +Learning means building/updating/re-balancing the model (the hard +part). Question answering is making (relatively simple) lookups +(geometrical queries) against the model.

-
-

4.1.2 Mapping of hyperspace to traditional object-oriented model

-
+
+

5.2 Mapping hypercube to object-oriented model and relational database

+

Object oriented programming is inspired by the way human mind operates. It allows programmer to express ideas to computer in a more @@ -410,120 +390,78 @@ human-like terms.

-It is possible to map object model to geometrical hyperspace: +It is actually also possible to map object model and relational +database to geometrical hyperspace:

    -
  • 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. +
  • Object or database table row is a point in hypercube arbitrary +dimensional space. Each object member variable or database table +column can be mapped to its own dimension in hypercube. That is: if +class declares 4 variables for an object, then corresponding object +can be stored as a single point inside 4 dimensional +hypercube. Variable values translate to point coordinates in that +hypercube. That is: numbers and string can be translated to linear +value that can be used as a coordinate along particular dimension.
    • -
  • 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. +
  • Each object class or database table declares its own hypercube that +contain instances (objects) of that class or rows of a table.
-
-

4.1.3 Handling of relations

-
+ +
+

5.3 Mapping entity relations in hypercube

+

-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: +Consider we want to create database of:

-
    -
  • Every dimension corresponds to one particular book author. (10 -authors in the database, would require 10 dimensional space) -
      -
    • Point in space corresponds to one particular book. -
        -
      • Point location along particular (author) dimension corresponds -to amount of work contributed by particular author for given -book. +
      • Books.
        • -
      +
    • Authors.
      • -
    +
  • Effort: Amount of time contributed by every author to every book +that he/she wrote.

-Alternatively: +Information above can be represented as 3D cube where dimensions are:

- -
    -
  • Every dimension corresponds to one particular book.
      -
    • Point in space corresponds to one particular author in the entire -database. -
        -
      • Point location along particular (book) dimension corresponds to -amount of work contributed for book by given author (point). +
      • X: Book
        • -
      +
    • Y: Author
      • -
    +
  • Z: Effort
-
-
-
-
-

4.2 Layered architecture

-
-
-
layer 1
disk / block storage / partition -
- -
layer 2
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. -
- -
layer 3
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) -
- -
layer 4
Implements arbitrary dimensional multiverse. -
- -
layer 5
Distributed computation engine. -
-
+

+Points in that cube would nicely capture many to many relations +between authors and the books. +

-
-

5 Current status

-
+
+

6 Current status

+
  • More or less defined Vision / goal.
    • -
  • Collected some ideas. +
  • Collected some inspiring ideas.
  • 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. +implement more advanced features on top of this via layered +architecture.
    • @@ -531,9 +469,9 @@ implement more advanced features on top of this.
-