<?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>Avro on Bits, Trades &amp; Systems</title>
    <link>https://blog.turboawesome.win/tags/avro/</link>
    <description>Recent content in Avro on Bits, Trades &amp; Systems</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 04 Oct 2018 11:29:00 +0000</lastBuildDate>
    <atom:link href="https://blog.turboawesome.win/tags/avro/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Schema Evolution in Avro: The Hard Lessons from Production</title>
      <link>https://blog.turboawesome.win/2018/10/schema-evolution-in-avro-the-hard-lessons-from-production/</link>
      <pubDate>Thu, 04 Oct 2018 11:29:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2018/10/schema-evolution-in-avro-the-hard-lessons-from-production/</guid>
      <description>Avro&amp;#39;s schema evolution rules sound simple. In production with multiple services and a regulated data retention requirement, the edges are sharp. Here are the cases that burned us and the practices that prevented future ones.</description>
    </item>
  </channel>
</rss>
