<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Kafka Streams</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Kafka Streams feed</description>
    <item>
      <title>Inside Atlassian Lithium: How a Dynamic ETL Platform is Transforming Data Movement and Cutting Costs</title>
      <link>https://www.infoq.com/news/2025/01/atlassian-lithium-etl/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Kafka+Streams</link>
      <description>&lt;img src="https://res.infoq.com/news/2025/01/atlassian-lithium-etl/en/headerimage/Atlassian-Header-1738065490770.jpg"/&gt;&lt;p&gt;Atlassian recently introduced Lithium, an in-house ETL platform designed to meet the requirements of dynamic data movement. Lithium streamlines tasks such as cloud migrations, scheduled backups, and in-flight data validations by supporting ephemeral pipelines and tenant-level isolation while ensuring efficiency and scalability, resulting in significant cost savings.&lt;/p&gt; &lt;i&gt;By Eran Stiller&lt;/i&gt;</description>
      <category>Atlassian</category>
      <category>ETL</category>
      <category>Data Pipelines</category>
      <category>Kafka Streams</category>
      <category>Apache Kafka</category>
      <category>Apache Flink</category>
      <category>AWS</category>
      <category>Architecture</category>
      <category>Reference Architecture</category>
      <category>Architecture &amp; Design</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>news</category>
      <pubDate>Wed, 29 Jan 2025 12:30:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2025/01/atlassian-lithium-etl/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Kafka+Streams</guid>
      <dc:creator>Eran Stiller</dc:creator>
      <dc:date>2025-01-29T12:30:00Z</dc:date>
      <dc:identifier>/news/2025/01/atlassian-lithium-etl/en</dc:identifier>
    </item>
  </channel>
</rss>
