This looks potentially fantastic.  If I could beg one wish from the developers of this (and almost every other project anywhere near this space), though, it would be one tiny piece of documentation:<p><i>What&#x27;s your unique ID scheme?</i><p>Let&#x27;s say I&#x27;m willing to believe[1] that you&#x27;ve got Durable and Consistent down, once messages make it committed <i>in</i> to the system.  What&#x27;s the story for messages on their way in?  My application logs are buffered to the local disk, now I&#x27;m streaming them into central storage, and halfway through a TCP connection that&#x27;s shuffled 2mb of thousands of messages into storage, the connection terminates -- unexpectedly, midmessage.  Could the service have committed <i>more</i> messages than it acknowledged?  Or many <i>less</i> than I&#x27;ve sent?  Both could be true from the network standpoint.[2]<p>So, what I need to know, and what should be <i>very</i> easy to answer, front-and-center in your docs, pretty please:<p>1) Where should my log uploader resume?<p>2) Is there any danger of repeatedly entering some lines?<p>3) If I have log lines that are legitimately duplicates, will they be stored at the correct count?<p>These are questions that may have a different answer than the durability <i>after</i> data makes it fully into the system.  It also may provide useful information about how complexity the code in a submitting client is, because good answers tend to require some kind of ID sequence being assigned on submitting clients, afaict.  And it&#x27;s really just plain critical to sanity.<p>----<p>[1] well, no, I&#x27;m not, &quot;trust by verify&quot; in all things etc etc; but let&#x27;s suppose that&#x27;s <i>more</i> believable and something I have to mechanically verify anyway, and doesn&#x27;t have an obviously observable boolean at the protocol level as to whether it&#x27;s going to work well or not, and system <i>internals</i> simply don&#x27;t have such a sordid history of being over-simplified until they&#x27;re broken like client interfaces so often are, so...!  We&#x27;ll handwave that to a later and more involved step of quality investigation.<p>[2] <a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Two_Generals&#x27;_Problem" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Two_Generals&#x27;_Problem</a>