Add: note that Muck is single-node only

1 files changed, 7 insertions, 1 deletions

diff --git a/README b/README
index 4ae0562..a510d8f 100644
--- a/README
+++ b/README
@@ -53,7 +53,13 @@ Architecture
 Muck is in essence a dict in memory, indexed by resource id, and an
 HTTP layer to allow it to be accessed. Any changes are logged to an
 append-only `changelog` file. At startup, the `changelog` is read and
-the changes are made to the dict.
+the changes are made to the dict. To backup and restore a Muck
+instance, or to move it to another host, the `changelog` is enough.
+
+Muck currently does not provide replication, sharding, or scalability
+to multiple nodes, or resiliency against its one node having problems
+or disappearing. These are valid concerns, which may be addressed
+later.
 
 There are currently no index data structures, so searches are very
 slow.