Started bringing up code designed to stream data from the data-ma-base directly
removed the log
Written something to consume those streams and keep pumping at them when new items go into them - seems legit
Initial stab at master->slave replication without etag preservation
Wrote some thoughts on replication
Demonstrated basic master -> slave workings in the repl
Thinking up more master/slave scenarios to test
Looking at getting feedback out of the slave
About to make a start on the replication loop to use the code I've managed to vomit out
Nearly factored out a persistent looping master->slave replicator function
stick null entries in the database for deleted docs
Inserting data for deleted documents
Handle deletions in master->slave replication
Properly handle deletions as part of the indexing process, although not really properly as it's a nil check and that is pretty horrid
Replication pulled into its own little thing and tested via the repl
Started adding tests around the master slave replication code written so far
Showing that paging will work
Test for replication from master to a newly started slave
Basic replication test works
We can count this as finished for master/slave replication - at least until we have vector clocks and can resolve conflicts