anchor.diff:  If `DTO` makes use of custom serialisation then you should specify the interface to write to with `-i`
   
   ''''
  -===== *High level interface for reading/writing*
  +==== High level interface for reading/writing
   
   Chronicle v4.4+ supports the use of proxies to write and read messages.
   You start by defining an asynchronous `interface`, where all methods have:
  
positive.code: //
  //*-* you have a record of all the decisions your new system is committed to; even if the new code would have made different decisions.
  
  ==== [big]#Detailed Guide#
  You can configure a Chronicle Queue using its configuration parameters or system properties. In addition, there are different ways of writing/reading into/from a queue such as the use of proxies and using `MethodReader` and `MethodWriter`.
  
  ===== ** [big]#Queue configuration#**
  
  Chronicle Queue (CQ) can be configured via a number of methods on the `SingleChronicleQueueBuilder` class.
  For complete list of configuration parameters and system properties, refer to https://github.com/ChronicleEnterprise/Chronicle-Queue-Enterprise-Demo/blob/master/docs/ConfigurationParameters.adoc#singlechroniclequeuebuilder[Configuration Parameters]. Please note that some configuration parameters on this page are only available for the Enterprise edition.
  
negative.code: 
  For more information on Chronicle Queue Enterprise Edition, please contact mailto:sales@chronicle.software[sales@chronicle.software].
  
  == User Guide
  
  A Chronicle Queue is defined by `SingleChronicleQueue.class` that is designed to support:
  
  *-* rolling files on a daily, weekly or hourly basis,
  
  *-* concurrent writers on the same machine,
  
  *-* concurrent readers on the same machine or across multiple machines via TCP replication (With Chronicle Queue Enterprise),
  
  *-* zero copy serialization and deserialization,
  
  *-* millions of writes/reads per second on commodity hardware.
  
  Approximately 5 million messages/second for 96-byte messages on a i7-4790 processor.
  A queue directory structure is as follows:
  
  [source]
  ----
  base-directory /
     {cycle-name}.cq4       - The default format is yyyyMMdd for daily rolling.
  ----
  
  The format consists of size-prefixed bytes which are formatted using `BinaryWire` or `TextWire`.
  Chronicle Queue is designed to be driven from code. You can easily add an interface which suits your needs.
  
  NOTE: Due to fairly low-level operation, Chronicle Queue read/write operations can throw unchecked exceptions. In order to prevent thread death, it might be practical to catch `RuntimeExceptions` and log/analyze them as appropriate.
  
  NOTE: For demonstrations of how Chronicle Queue can be used see link:https://github.com/OpenHFT/Chronicle-Queue-Sample[Chronicle Queue Demo] and for Java documentation see link:https://www.javadoc.io/doc/net.openhft/chronicle-queue/latest/index.html[Chronicle Queue JavaDocs]
  
  In the following sections, first we introduce some terminology and a quick reference to use Chronicle Queue. Then, we provide a more detailed guide.
  
  === Key Concepts and Terminology
  Chronicle Queue is a persisted journal of messages which supports concurrent writers and readers even across multiple JVMs on the same machine.
  