<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="https://umn7fc98gj7rc.julianrbryant.com/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Distributed Systems</title>
    <link>https://un5gmtkzgjn63apf3w.julianrbryant.com</link>
    <description>InfoQ Distributed Systems feed</description>
    <item>
      <title>Article: Replacing Database Sequences at Scale Without Breaking 100+ Services</title>
      <link>https://un5gmtkzgjn63apf3w.julianrbryant.com/articles/replacing-database-sequences/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Distributed+Systems</link>
      <description>&lt;img src="https://un5pmbagwnwm69a3.julianrbryant.com/articles/replacing-database-sequences/en/headerimage/replacing-database-sequences-header-1774603762739.jpg"/&gt;&lt;p&gt;The article discusses the challenges faced during a migration from a relational database to NoSQL, focusing on the importance of database sequences for unique identifiers. It outlines the development of a new sequence service using DynamoDB and a two-tier caching architecture.&lt;/p&gt; &lt;i&gt;By Saumya Tyagi&lt;/i&gt;</description>
      <category>AWS</category>
      <category>Dynamo DB</category>
      <category>NoSQL</category>
      <category>Distributed Systems</category>
      <category>Caching</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>article</category>
      <pubDate>Fri, 03 Apr 2026 09:00:00 GMT</pubDate>
      <guid>https://un5gmtkzgjn63apf3w.julianrbryant.com/articles/replacing-database-sequences/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Distributed+Systems</guid>
      <dc:creator>Saumya Tyagi</dc:creator>
      <dc:date>2026-04-03T09:00:00Z</dc:date>
      <dc:identifier>/articles/replacing-database-sequences/en</dc:identifier>
    </item>
    <item>
      <title>Article: Event-Driven Patterns for Cloud-Native Banking: Lessons from What Works and What Hurts</title>
      <link>https://un5gmtkzgjn63apf3w.julianrbryant.com/articles/event-driven-banking-architecture/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Distributed+Systems</link>
      <description>&lt;img src="https://un5pmbagwnwm69a3.julianrbryant.com/articles/event-driven-banking-architecture/en/headerimage/event-driven-banking-architecture-header-1774430827143.jpg"/&gt;&lt;p&gt;Event-driven architecture helps banks decouple systems, scale services, and create clear activity trails. But it also introduces complexity, new failure modes, and operational challenges. Chris Tacey-Green explains where it adds value in banking systems and the practical patterns, such as inbox/outbox and stable event contracts, needed to make it reliable.&lt;/p&gt; &lt;i&gt;By Chris Tacey-Green&lt;/i&gt;</description>
      <category>QCon Software Development Conference</category>
      <category>Banking</category>
      <category>Platform Engineering</category>
      <category>Event Driven Architecture</category>
      <category>Financial Applications</category>
      <category>AWS</category>
      <category>Distributed Systems</category>
      <category>Cloud Native Architecture</category>
      <category>Cloud</category>
      <category>InfoQ Dev Summit Munich 2025</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>article</category>
      <pubDate>Tue, 31 Mar 2026 09:00:00 GMT</pubDate>
      <guid>https://un5gmtkzgjn63apf3w.julianrbryant.com/articles/event-driven-banking-architecture/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Distributed+Systems</guid>
      <dc:creator>Chris Tacey-Green</dc:creator>
      <dc:date>2026-03-31T09:00:00Z</dc:date>
      <dc:identifier>/articles/event-driven-banking-architecture/en</dc:identifier>
    </item>
    <item>
      <title>Discord Engineers Add Distributed Tracing to Elixir's Actor Model without Performance Penalty</title>
      <link>https://un5gmtkzgjn63apf3w.julianrbryant.com/news/2026/03/discord-elixir-actor-tracing/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Distributed+Systems</link>
      <description>&lt;img src="https://un5gmtkzgjn63apf3w.julianrbryant.com/styles/static/images/logo/logo_bigger.jpg"/&gt;&lt;p&gt;Discord engineering detailed how they added distributed tracing to Elixir's actor model. Their custom Transport library wraps messages with trace context and uses dynamic sampling to handle million-user fanouts. CPU optimizations included skipping unsampled traces and filtering context before deserialization, recovering 10+ percentage points of overhead.&lt;/p&gt; &lt;i&gt;By Steef-Jan Wiggers&lt;/i&gt;</description>
      <category>Elixir</category>
      <category>Performance</category>
      <category>Observability</category>
      <category>Distributed Systems</category>
      <category>Actor Model</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>DevOps</category>
      <category>news</category>
      <pubDate>Sat, 28 Mar 2026 10:13:00 GMT</pubDate>
      <guid>https://un5gmtkzgjn63apf3w.julianrbryant.com/news/2026/03/discord-elixir-actor-tracing/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Distributed+Systems</guid>
      <dc:creator>Steef-Jan Wiggers</dc:creator>
      <dc:date>2026-03-28T10:13:00Z</dc:date>
      <dc:identifier>/news/2026/03/discord-elixir-actor-tracing/en</dc:identifier>
    </item>
    <item>
      <title>Inside Agoda’s Storefront: a Latency-Aware  Reverse Proxy for Improving DNS Based Load Distribution</title>
      <link>https://un5gmtkzgjn63apf3w.julianrbryant.com/news/2026/03/agoda-rust-reverse-proxy/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Distributed+Systems</link>
      <description>&lt;img src="https://un5pmbagwnwm69a3.julianrbryant.com/news/2026/03/agoda-rust-reverse-proxy/en/headerimage/generatedHeaderImage-1773552076467.jpg"/&gt;&lt;p&gt;Agoda engineers developed Storefront, a Rust-based S3-compatible reverse proxy that improves load balancing, request routing, and observability across large-scale object storage systems. The proxy addresses DNS-based distribution limitations, implements latency-aware routing, cross-data-center optimizations, IO safeguards, credential-less authentication, and exposes telemetry via OpenTelemetry.&lt;/p&gt; &lt;i&gt;By Leela Kumili&lt;/i&gt;</description>
      <category>Rust</category>
      <category>S3</category>
      <category>Optimization</category>
      <category>Load Balancing</category>
      <category>Kubernetes</category>
      <category>Low Latency</category>
      <category>Cloud Tech</category>
      <category>Distributed Systems</category>
      <category>Telemetry</category>
      <category>DNS</category>
      <category>Object Databases</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>news</category>
      <pubDate>Fri, 27 Mar 2026 14:11:00 GMT</pubDate>
      <guid>https://un5gmtkzgjn63apf3w.julianrbryant.com/news/2026/03/agoda-rust-reverse-proxy/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Distributed+Systems</guid>
      <dc:creator>Leela Kumili</dc:creator>
      <dc:date>2026-03-27T14:11:00Z</dc:date>
      <dc:identifier>/news/2026/03/agoda-rust-reverse-proxy/en</dc:identifier>
    </item>
  </channel>
</rss>
