<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Distributed Systems - News</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Distributed Systems News feed</description>
    <item>
      <title>Slack Outlines Four-Phase Journey to a Multi-Cloud AI Serving Platform</title>
      <link>https://www.infoq.com/news/2026/06/slack-multicloud/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Distributed+Systems-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/06/slack-multicloud/en/headerimage/generatedHeaderImage-1782335922071.jpg"/&gt;&lt;p&gt;Slack has outlined how its AI serving infrastructure evolved through four distinct phases, moving from a self-managed Amazon SageMaker deployment to a multi-cloud architecture spanning AWS Bedrock and Google Cloud Vertex AI.&lt;/p&gt; &lt;i&gt;By Matt Foster&lt;/i&gt;</description>
      <category>Cloud</category>
      <category>Distributed Systems</category>
      <category>Cloud Architecture</category>
      <category>Performance &amp; Scalability</category>
      <category>Large language models</category>
      <category>Architecture &amp; Design</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Thu, 25 Jun 2026 07:02:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/06/slack-multicloud/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Distributed+Systems-news</guid>
      <dc:creator>Matt Foster</dc:creator>
      <dc:date>2026-06-25T07:02:00Z</dc:date>
      <dc:identifier>/news/2026/06/slack-multicloud/en</dc:identifier>
    </item>
    <item>
      <title>Inside Atlassian’s Forge Billing Architecture for Distributed Usage Tracking at Scale</title>
      <link>https://www.infoq.com/news/2026/06/forge-billing-usage-platform/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Distributed+Systems-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/06/forge-billing-usage-platform/en/headerimage/generatedHeaderImage-1780198060365.jpg"/&gt;&lt;p&gt;Atlassian details the Forge billing platform built for usage-based pricing across its cloud ecosystem. It processes large-scale usage events with correct attribution, deduplication, and aggregation using a streaming pipeline, idempotent processing, and layered storage to enable accurate billing, near real-time visibility, and reliable reconciliation across distributed services.&lt;/p&gt; &lt;i&gt;By Leela Kumili&lt;/i&gt;</description>
      <category>Jira</category>
      <category>Apache Kafka</category>
      <category>SaaS</category>
      <category>Cloud Architecture</category>
      <category>Distributed Systems</category>
      <category>FinOps</category>
      <category>Observability</category>
      <category>Streaming</category>
      <category>Event Stream Processing</category>
      <category>Event Driven Architecture</category>
      <category>Atlassian</category>
      <category>Multi-tenancy</category>
      <category>Architecture &amp; Design</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Sat, 20 Jun 2026 14:21:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/06/forge-billing-usage-platform/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Distributed+Systems-news</guid>
      <dc:creator>Leela Kumili</dc:creator>
      <dc:date>2026-06-20T14:21:00Z</dc:date>
      <dc:identifier>/news/2026/06/forge-billing-usage-platform/en</dc:identifier>
    </item>
    <item>
      <title>Behind the Scenes:  Block 450 JVM Repositories into Monorepo to Reduce Dependency Drift</title>
      <link>https://www.infoq.com/news/2026/06/block-450-jvm-monorepo-migration/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Distributed+Systems-news</link>
      <description>&lt;img src="https://www.infoq.com/styles/static/images/logo/logo_bigger.jpg"/&gt;&lt;p&gt;Block, Inc. describes migrating ~450 JVM repositories into a monorepo across Cash App and Square engineering to reduce dependency drift and coordination overhead. The system supports ~8,800 weekly builds with ~10 min p90 CI time. The approach improves cross-service changes, build visibility, and developer experience through dependency graph–based builds, selective CI, and custom IDE tooling.&lt;/p&gt; &lt;i&gt;By Leela Kumili&lt;/i&gt;</description>
      <category>Continuous Integration</category>
      <category>Build systems</category>
      <category>Platform Engineering</category>
      <category>IntelliJ IDEA</category>
      <category>IDE</category>
      <category>Distributed Systems</category>
      <category>Continuous Deployment</category>
      <category>JVM</category>
      <category>Java</category>
      <category>Large Projects</category>
      <category>plugins</category>
      <category>Architecture &amp; Design</category>
      <category>Development</category>
      <category>DevOps</category>
      <category>news</category>
      <pubDate>Fri, 19 Jun 2026 14:47:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/06/block-450-jvm-monorepo-migration/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Distributed+Systems-news</guid>
      <dc:creator>Leela Kumili</dc:creator>
      <dc:date>2026-06-19T14:47:00Z</dc:date>
      <dc:identifier>/news/2026/06/block-450-jvm-monorepo-migration/en</dc:identifier>
    </item>
  </channel>
</rss>
