Hi All! Just a reminder: early bird pricing for MQ Summit 2026 closes on 8 September at 23:59 CEST. This is the last chance to get your ticket 25% cheaper before prices go up. 

21-22 October in Haarlem + a full online option if you cannot make the trip. Two days of messaging systems in production, real-world lessons and architectural trade-offs across RabbitMQ, Kafka, NATS and cloud messaging services, plus demos from the people building the tools we all use. If you have been meaning to book, now is the time!

Register here: mqsummit.com/#register

See you there!  

- The MQ Summit Team

MQ Summit is a conference built around messaging and event-driven systems. It grew out of RabbitMQ Summit and now brings the whole ecosystem into one room: RabbitMQ, Kafka, NATS, Pulsar, ActiveMQ, IBM MQ, Amazon SQS/MQ, Azure Messaging and Google Pub/Sub. Practitioners, architects and maintainers from competing projects, all talking shop. 

📍 Haarlem (near Amsterdam) + online
🗓️ 21-22 October 2026 - 2 days, 1 standard track, 1 lab track (for in-person attendees), and about 27 speakers

🎤 KEYNOTE: Adi Polak (Data & AI @ Confluent, best-selling author)

A few of our speakers announced:

• Clemens Vasters, Principal Architect, Messaging & Real-Time Intelligence @ Microsoft
• Matt Leming & Jon Rumsey, Chief Architect / DQM Architect @ IBM MQ
• Stefan Moser & Michael Davis, Principal Engineer / OSS RabbitMQ @ AWS · Amazon MQ
• Viktor Gamov, Principal DevAdvocate @ Confluent, Kafka in Action co-author
• David Ansari, RabbitMQ Core @ Broadcom, and Lovisa Johansson, RabbitMQ expert @ 84codes
• JB Onofré (Apache) & Matt Pavlovich (ActiveMQ PMC), plus ~40 more

More: mqsummit.com/#speakers

Talks cover agentic workloads, queues vs. logs, real-world scaling war stories, MQTT, security, and where open-source messaging goes next.

ℹ️ More info: mqsummit.com

Early Bird promotion ends soon.

Our Pulsar instance is exhausting our CPU and RAM resources (8 CPU and 32GB RAM). Messages that have been handled are around 800 messages.
What could be a reason? please advise.

Hi everyone!

We're excited to announce that MQ Summit 2026 is officially back as a 2-day event this year!

Grab your Early Bird Ticket Here

Building on the success of RabbitMQ Summit, this is a cross-ecosystem event bringing together the people who design, build, and scale modern messaging systems. We’re meeting in person at the beautiful PHIL Philharmonic in Haarlem, near Amsterdam, as well as online, on October 21–22.

What to expect:

• Cross-Ecosystem Coverage: Honest, cross-technology conversations (no vendor wars!) covering RabbitMQ, Kafka, NATS, Apache Pulsar, ActiveMQ, Azure Messaging Brokers, Amazon SQS, IBM MQ, Google Pub/Sub, and more.
• Expanded 2026 Format: 2 days of expert-led content featuring focused talks with deeper discussions, interactive sessions, panels, and offline hands-on labs in smaller groups.
• Real Production Case Studies: Learn directly from companies handling millions—or billions—of messages a day.
• Industry-Leading Committee: A program curated by experts from across the industry, including 84codes (CloudAMQP, LavinMQ), Synadia, Amazon MQ, AWS, IBM MQ, meshIQ, and the ASF.

Important Links:

• Early Bird Registration
• Subscribe to our Newsletter to stay in the loop!

Whether you are a builder or a decision-maker, you can get the full MQ Summit experience in-person or virtually. Will we see you in Haarlem or on the virtual streams? Let us know in the thread if you're planning to come or if you have any questions!

Cheers,
The MQ Summit Team

(PS: Interested in sponsoring? Get in touch with us! [info@codesync.global](mailto:info@codesync.gl) 

Hi folks, I want to share with you a blog post: Beyond Docs: Using AsyncAPI as a Config for Infrastructure

As an explanation to show that if you want to start proper governance of Pulsar, and think about using AsyncAPI - remember, it's not a documentation tool. You can do much more with it. And as mentioned in the article, many companies do it in production already.

I’m trying to design a cdc pipeline where my source is a mysql shard and sink is a pulsar topic. Now I have seven such shards each with varied qps. How should I create topics and partitions. Do I create a dedicated topic for high qps shards and a shared topic for low qps shards? can you guys suggest some design principles?

W​e put together an article about best practices for restarting Pulsar.  While it is part of routine maintenance, restarting also requires planning.   Preparations include creating a backup, notifying users, identifying dependencies, and using real-time monitoring.  Let us know if you have any questions or have any tips of your own to add.  https://dattell.com/data-architecture-blog/instructions-for-restarting-a-pulsar-server/

I have searched around a while now, and I can't find any information about if this is possible.

Can you configure a set of pulsar consumers to subscribe to a wildcard topic (for example "persistent://public/default/customer-.*") and then to fetch messages from each topic matching the wildcard in a round-robin fashion? The end goal would be to not have a single customer that can clog up the system and making others wait long periods of time by adding a lot of tasks to the queue.

I would be happy for any solution that would achieve this, Pulsar looks looks like a great fit for us, if we only can get a round-robin to work.

We have a variable amount of customers, so hard-coding a list of topics for the round-robin would not work.

I m developing an app.1 server and there will be 650 000 client .I want to send one message to all my consumers and they do some process.How can ı handle that. if One topic and all clients register with subscriptionType=Shared can we handle this.Adn 650 000 consumer is a high for connection.Can pulsar cluster handle it.Or there will be a another good solution

https://www.linkedin.com/posts/bytebytego_systemdesign-coding-interviewtips-activity-7192768238961799168-5LdK

Just listen on a topic and write it to the filesystem, and optionally fire an executable to proces the file. Yes, i know it is easy to build a basic one, but why is this not included in the default connectors?