anchor.diff:  
   Chronicle works best in SEDA style event driven systems, where latency is critical and you need a record of exactly what was performed when. (Without expensive network sniffing/recording systems)
   
  -=== What is the performance like?
  -While Vanilla and Index Chronicle support sub-microsecond latencies. If you use Wire, the typical latencies tend to be around one micro-second.  You can still use raw writing of bytes if you need maximum performance.
  -
   === With a tight reader loop I see 100% utilization, will there be processing capability left for anything else ?
   
   Two approaches for reducing CPU usage are;
  
positive.code: what should the client do with the historical responses on startup?
  some heartbeat system so that client knows the server is alive
  archiving of the old queues (`VanillaChronicle` makes it easier at some cost).
  
  === What types of Excerpt are there?
  
  
negative.code: 
  However, this could be an overkill, especially if you don't have to keep the history of the request/responses. 
  
  Imagine a simple scenario with two processes: `C` (client) and `S` (server). Create two `SingleChronicleQueue`s:
  
  `Q1` for sending requests from `C` to `S`
  `Q2` for sending responses from `S` to `C`
  