From aeb8a58fbe6a54ae99d8dcca3f2100d5ce50c3ed Mon Sep 17 00:00:00 2001
From: Neil Clifford <neil.clifford@chronicle.software>
Date: Wed, 4 Oct 2017 16:08:16 +0100
Subject: [PATCH] Initial re-work of documentation

---
 docs/CM_Overview.adoc                     | 50 -----------------------
 docs/{ => archived}/CM_Compatibility.adoc |  0
 docs/{ => archived}/CM_Versioning.adoc    |  0
 3 files changed, 50 deletions(-)
 delete mode 100755 docs/CM_Overview.adoc
 rename docs/{ => archived}/CM_Compatibility.adoc (100%)
 rename docs/{ => archived}/CM_Versioning.adoc (100%)

diff --git a/docs/CM_Overview.adoc b/docs/CM_Overview.adoc
deleted file mode 100755
index 8b256f514..000000000
--- a/docs/CM_Overview.adoc
+++ /dev/null
@@ -1,50 +0,0 @@
-= Chronicle Map overview
-
-Chronicle Map is a super-fast, in-memory, key-value
-store, that can overflow seamlessly to disk, and can be distributed across the network.
-
-image::images\CM_Overview.jpg[]
-
-== Use cases
-Chronicle Map is used in production around the
-world for:
-
-• **real-time trading systems**. Chronicle Map
-provides in-memory access speeds, and supports
-ultra-low garbage collection. Chronicle Map can support the most demanding of applications.
-• **highly concurrent systems**. Chronicle Map
-supports multiple readers and writers,
-distributed across multiple machines.
-
-== Why use Chronicle Map?
-Chronicle Map is:
-
-• fast. Millions of operations per second, with
-low and stable microsecond latencies.
-• built using lessons learnt from real-world
-experience solving real-world problems.
-• open source (standard version), and in use at
-hundreds of sites around the world.
-• in production at banks and hedge funds,
-globally.
-• reliable. Chronicle Software have a “chaos
-monkey” test which verifies Chronicle Map
-multi-master replication in the face of node
-and network failures.
-
-== Our offering
-Chronicle Software provide full support for
-Chronicle Map, consulting to help you make
-best use of the product, and can also deliver
-projects using a mix of our resources and
-your own.
-
-== Replication Environment Example
-The following diagram shows an example of Chronicle Map replication over 3 servers (or sites).
-
-image::images\Configure_Three_Way_Replication.png[]
-
-Replication is multi-master, lock-free, redundant, deterministic, and eventually consistent.
-
-The writer can optionally wait for replication to occur across nodes or regions.
-
diff --git a/docs/CM_Compatibility.adoc b/docs/archived/CM_Compatibility.adoc
similarity index 100%
rename from docs/CM_Compatibility.adoc
rename to docs/archived/CM_Compatibility.adoc
diff --git a/docs/CM_Versioning.adoc b/docs/archived/CM_Versioning.adoc
similarity index 100%
rename from docs/CM_Versioning.adoc
rename to docs/archived/CM_Versioning.adoc