<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Performance - News</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Performance News feed</description>
    <item>
      <title>30+ Updates per Second per Account: Uber Scales Ledger Processing with Batching</title>
      <link>https://www.infoq.com/news/2026/06/uber-payment-batching-system/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Performance-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/06/uber-payment-batching-system/en/headerimage/generatedHeaderImage-1779570527807.jpg"/&gt;&lt;p&gt;Uber introduced a high-throughput financial ledger processing system designed to handle hot account write contention at scale. Using 250ms batching, Redis coordination, and optimistic atomic updates, the system supports 30+ updates per second per account while preserving consistency and auditability, reducing multi-hour processing pipelines to minutes in its distributed accounting infrastructure.&lt;/p&gt; &lt;i&gt;By Leela Kumili&lt;/i&gt;</description>
      <category>Transactions Processing</category>
      <category>Optimization</category>
      <category>Distributed Systems</category>
      <category>HotSpot</category>
      <category>Consistency</category>
      <category>Performance</category>
      <category>Event Driven Architecture</category>
      <category>payment</category>
      <category>Low Latency</category>
      <category>Event Stream Processing</category>
      <category>Financial Applications</category>
      <category>Batch Processing</category>
      <category>Architecture &amp; Design</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Thu, 04 Jun 2026 14:02:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/06/uber-payment-batching-system/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Performance-news</guid>
      <dc:creator>Leela Kumili</dc:creator>
      <dc:date>2026-06-04T14:02:00Z</dc:date>
      <dc:identifier>/news/2026/06/uber-payment-batching-system/en</dc:identifier>
    </item>
    <item>
      <title>Shopify Reports 15X Faster Graphql Execution with Breadth First Engine</title>
      <link>https://www.infoq.com/news/2026/06/shopify-graphql-cardinal-bfs/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Performance-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/06/shopify-graphql-cardinal-bfs/en/headerimage/generatedHeaderImage-1779561076024.jpg"/&gt;&lt;p&gt;Shopify introduced GraphQL Cardinal, a new execution engine replacing depth-first traversal with breadth-first execution. The redesign improves large-scale GraphQL performance with up to 15x faster field execution, 6x lower GC overhead, and +4s P50 latency gains. It focuses on execution-layer efficiency and batched resolver processing for high-cardinality commerce queries.&lt;/p&gt; &lt;i&gt;By Leela Kumili&lt;/i&gt;</description>
      <category>Optimization</category>
      <category>API</category>
      <category>Distributed Systems</category>
      <category>Platform Engineering</category>
      <category>Search</category>
      <category>Performance</category>
      <category>Low Latency</category>
      <category>GraphQL</category>
      <category>Microservices</category>
      <category>Architecture &amp; Design</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Mon, 01 Jun 2026 14:25:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/06/shopify-graphql-cardinal-bfs/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Performance-news</guid>
      <dc:creator>Leela Kumili</dc:creator>
      <dc:date>2026-06-01T14:25:00Z</dc:date>
      <dc:identifier>/news/2026/06/shopify-graphql-cardinal-bfs/en</dc:identifier>
    </item>
  </channel>
</rss>
