<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - RabbitMQ - News</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ RabbitMQ News feed</description>
    <item>
      <title>QCon London 2025: the Origin Story of AMQP - Advanced Message Queuing Politics</title>
      <link>https://www.infoq.com/news/2025/04/origin-advanced-message-queuing/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=RabbitMQ-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2025/04/origin-advanced-message-queuing/en/headerimage/generatedHeaderImage-1744217027281.jpg"/&gt;&lt;p&gt;Join John O'Hara, creator of the Advanced Message Queuing Protocol (AMQP), as he shares the compelling journey of this groundbreaking technology at QCon London. Discover the intricate dynamics of collaboration, challenges faced, and the human element in open standards. O'Hara's insights illuminate the politics behind technology development, proving vision is as vital as innovation.&lt;/p&gt; &lt;i&gt;By Steef-Jan Wiggers&lt;/i&gt;</description>
      <category>Protocol</category>
      <category>Queue</category>
      <category>Cloud</category>
      <category>AMQP</category>
      <category>RabbitMQ</category>
      <category>Messaging</category>
      <category>Azure</category>
      <category>QCon London 2025</category>
      <category>DevOps</category>
      <category>Architecture &amp; Design</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Sat, 12 Apr 2025 11:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2025/04/origin-advanced-message-queuing/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=RabbitMQ-news</guid>
      <dc:creator>Steef-Jan Wiggers</dc:creator>
      <dc:date>2025-04-12T11:00:00Z</dc:date>
      <dc:identifier>/news/2025/04/origin-advanced-message-queuing/en</dc:identifier>
    </item>
  </channel>
</rss>
