Skip to Main Content
IBM Data Platform Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data Platform organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:


Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,


Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com



Status Submitted
Created by Guest
Created on Feb 26, 2024

Asynchronous suspect duplicate processing -Move away from MQ/SIB Queues to Kafka

Recommendation: Transition from MQ/SIB to Kafka for Asynchronous Processing

The current implementation using MQ/SIB queues is introducing risks around duplicate processing and is not optimal from a performance and scalability standpoint.

Given that Kafka is already established within the ANZ ecosystem, continuing to maintain a separate messaging stack solely for this functionality creates unnecessary operational overhead, complexity, and inconsistency in the architecture.

Strong Recommendation:
We should strategically move away from MQ/SIB queues and standardize on Kafka for asynchronous processing. This will:

  • Reduce the risk of duplicate message processing

  • Improve performance, scalability, and resilience

  • Align with existing ANZ platform standards

  • Eliminate the need to support and maintain a parallel messaging infrastructure

Maintaining a separate asset for this specific use case is not justified when a robust, enterprise-grade solution already exists within the ecosystem.

TS015497881

Needed By Quarter