Jon Rumsey

Distributed Queue Manager Architect, IBM MQ

Jon has worked for IBM in MQ development since 1999 and has worked on every release of IBM MQ since across a variety of platforms including AIX, OS/400, Linux Intel/PPC/s390x, HP-UX, Solaris SPARC/Itanium, HP NonStop Kernel, MacOS & Windows.

Jons current role is architect for the distributed queue manager and is responsible for MQs data persistence, integrity and transactionality.

Jon still enjoys the deeply technical side of the job, designing and developing new product features and fixes.

Talk:
Get Hands-on with the IBM MQ AI Agent (lab)

Meet the IBM MQ Agent, your digital coworker for MQ operations. In this session you’ll be guided by the MQ Agent to investigate realistic problem scenarios, explore the associated MQ configuration, and interrogate the Agent’s extensive product domain knowledge. The lab will also demonstrate how recent MQ and Agent enhancements, such as remote retrieval of queue manager error log data, can be utilised to drive MQ insights and augment ops team skills to drive operational efficiency.

Key Takeaways:

  • Attendees will gain first-hand experience how AI can be applied to messaging components in a ‘production solution’ in identifying the root cause of a problem report.

Target Audience:

  • Administrators, developers, CTOs and leaders interested in operational efficiency.

Talk:
Resilient Messaging... How Hard Can It Be?

Transactions, persistence and availability are all fairly easy to manage when there is only one server. However, the bar is much higher for messaging solutions - they’re expected to just be there and trusted to transport valuable data. What happens when a disk fails? the network fails? a node fails? or worse case - your entire data centre fails?

Key Takeaways:

  • The audience will be able to learn how MQ achieves the basics like message persistence and transactionality using a recovery log. The talk will then cover what happens when components fail, how can MQ provide redundancy, look at the difference between message and service availability and how IBM implemented raft based distributed consensus.

Target Audience:

  • All messaging enthusiasts! Architects, developers and ops roles who have a curiosity in how message queuing works.