<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Persistence on Bits, Trades &amp; Systems</title>
    <link>https://blog.turboawesome.win/tags/persistence/</link>
    <description>Recent content in Persistence on Bits, Trades &amp; Systems</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 21 Jan 2015 10:44:00 +0000</lastBuildDate>
    <atom:link href="https://blog.turboawesome.win/tags/persistence/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Chronicle Queue vs Kafka: Choosing a Persistent Journal at Nanosecond Scale</title>
      <link>https://blog.turboawesome.win/2015/01/chronicle-queue-vs-kafka-choosing-a-persistent-journal-at-nanosecond-scale/</link>
      <pubDate>Wed, 21 Jan 2015 10:44:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2015/01/chronicle-queue-vs-kafka-choosing-a-persistent-journal-at-nanosecond-scale/</guid>
      <description>Both Chronicle Queue and Kafka provide persistent, ordered message logs. Their performance profiles, operational models, and use cases are almost completely different.</description>
    </item>
    <item>
      <title>Java Chronicle: Off-Heap Persistence Without Serialisation Overhead</title>
      <link>https://blog.turboawesome.win/2013/09/java-chronicle-off-heap-persistence-without-serialisation-overhead/</link>
      <pubDate>Thu, 05 Sep 2013 14:22:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2013/09/java-chronicle-off-heap-persistence-without-serialisation-overhead/</guid>
      <description>Chronicle Map and Chronicle Queue use memory-mapped files to give you persistent storage that doesn&amp;#39;t touch the GC heap. Here&amp;#39;s how we used it for trade journaling at microsecond latency.</description>
    </item>
  </channel>
</rss>
