X-Git-Url: http://www2.svjatoslav.eu/gitweb/?p=sixth.git;a=blobdiff_plain;f=doc%2Findex.html;h=e84f6268c11b3c46dd80d8d2438f05bd530b35f5;hp=984458351b32b79eebb6b60d2527e4c838804a86;hb=d7abb2f5dfabd382d37a31a9a52a0f0654b44c48;hpb=4198ad4b1cc7ec5aaf6919b503ce5c0c99b3ff5c diff --git a/doc/index.html b/doc/index.html index 9844583..e84f626 100644 --- a/doc/index.html +++ b/doc/index.html @@ -2,7 +2,7 @@ Sixth - system for data storage, computation, exploration and interaction - + @@ -243,17 +243,41 @@ Dr. Lawrence Angelo, The Lawnmower Man (1992)

+ +
  • Why such name ? + +
    • -

    1.1 Perfect data storage and computation engine

    +

    -I love thease existing solutions and properties: +I hate to choose between good things. Figuring out a way to combine +below properties in one system would be beyond awesome. +

    + +

    +(That`s the high level overview, details are slowly being worked +out…)

    +
    +
    +

    1.1.1 Computation

    +
    • Lisp (programming language):
        @@ -280,6 +304,35 @@ fly.
      • +
    • Hadoop (computation system): +
        +
      • Many individual connected computers behave as one big +computer. System is horizontally linearly scalable. +
        • +
      • Programming abstraction and execution model that naturally divides +problems te be solved in parallel and result easily combined. +
        • +
      • Data is spread across nodes, automatic failover, built in +resiliency. +
        • +
      • Small pieces of code are automatically transferred to the node +that contains relatively big data that needs processing (network +efficiency). +
        • +
      +
      • +
    +
    +
    + +
    +

    1.1.2 Data storage

    +
    +

    +See: Sixth data subproject +

    + +
    • Relational databases:
      • Transactional @@ -302,38 +355,12 @@ fly.
      • - -
    • Hadoop (computation system): -
        -
      • Many individual connected computers behave as one big -computer. System is horizontally linearly scalable. -
        • -
      • Programming abstraction and execution model that naturally divides -problems te be solved in parallel and result easily combined. -
        • -
      • Data is spread across nodes, automatic failover, built in -resiliency. -
        • -
      • Small pieces of code are automatically transferred to the node -that contains relatively big data that needs processing (network -efficiency). -
      -
      • -
    - - -

    -I hate to choose between good things. Figuring out a way to combine -above properties in one system would be beyond awesome. -

    - -

    -(I have not solved it yet..) -

    + +

    2 Current status

    @@ -343,7 +370,7 @@ above properties in one system would be beyond awesome.
  • In the process of implementing some of building blocks: