From e9ca1aaef242d490b788e69b521da0aa700c874a Mon Sep 17 00:00:00 2001 From: Svjatoslav Agejenko Date: Thu, 25 May 2017 22:08:38 +0300 Subject: [PATCH] Better documentation layout. --- doc/index.html | 79 ++++++++++++++++++++++++++++++-------------------- doc/index.org | 37 +++++++++++++---------- 2 files changed, 68 insertions(+), 48 deletions(-) diff --git a/doc/index.html b/doc/index.html index 9844583..6bb7dda 100644 --- a/doc/index.html +++ b/doc/index.html @@ -2,7 +2,7 @@ Sixth - system for data storage, computation, exploration and interaction - + @@ -250,10 +250,21 @@ Dr. Lawrence Angelo, The Lawnmower Man (1992)

1.1 Perfect data storage and computation engine

+ +

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

+

-I love thease existing solutions and properties: +(That`s the high level overview, details are slowly being worked +out…)

+
+
+

1.1.1 Computation

+
  • Lisp (programming language):
      @@ -280,6 +291,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 +342,13 @@ 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 +358,7 @@ above properties in one system would be beyond awesome.
  • In the process of implementing some of building blocks:
    • diff --git a/doc/index.org b/doc/index.org index bd143a8..a1cbfb9 100644 --- a/doc/index.org +++ b/doc/index.org @@ -46,8 +46,14 @@ In short, this is what I want: :PROPERTIES: :ID: 4224d52c-2ee1-411a-bd89-77c286322b21 :END: -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...) + +*** Computation + Lisp (programming language): + Almost no syntax. + Code and data intercangeable. @@ -60,17 +66,6 @@ I love thease existing solutions and properties: + Anything can be suspended/resumed from persistent storage on the fly. -+ Relational databases: - + Transactional - + Indexable / Quickly searchable - -+ Git (version control system) - + Versionable - + Branchable / mergeable. - + Transparent cansistency, checksumming and deduplication. - + (Git as a database: - https://www.kenneth-truyers.net/2016/10/13/git-nosql-database/ ) - + Hadoop (computation system): + Many individual connected computers behave as one big computer. System is horizontally linearly scalable. @@ -82,16 +77,26 @@ I love thease existing solutions and properties: that contains relatively big data that needs processing (network efficiency). +*** Data storage +See: [[http://www2.svjatoslav.eu/gitbrowse/sixth-data/doc/index.html][Sixth data subproject]] + ++ Relational databases: + + Transactional + + Indexable / Quickly searchable + ++ Git (version control system) + + Versionable + + Branchable / mergeable. + + Transparent cansistency, checksumming and deduplication. + + (Git as a database: + https://www.kenneth-truyers.net/2016/10/13/git-nosql-database/ ) -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..) * Current status + Formulated high-level [[id:1f4e1c17-d25f-4d92-aa9b-5785f1d86f4f][vision / goal]]. + In the process of implementing some of building blocks: - - [[http://www2.svjatoslav.eu/gitbrowse/sixth-data/doc/index.html][First layer of storage: Simple persistent key-value map.]] + - [[http://www2.svjatoslav.eu/gitbrowse/sixth-data/doc/index.html][Data storage engine.]] - [[http://www2.svjatoslav.eu/gitbrowse/sixth-3d/doc/index.html][In software, pure Java realtime 3D rendering engine.]] - [[http://www2.svjatoslav.eu/gitbrowse/sixth-3d-demos/doc/index.html][3D engine demos]] -- 2.20.1