IBM MQ is used as an Enterprise Messaging platform in a Banking organization to ensure message integrity and flow consistency. It deals with challenges such as long-running transactions, message tracking, performance, and authentication/authorization issues. Working with IBM MQ for many years in heterogeneous environments, the platform has proven to be robust, with huge integration capabilities through the variety of APIs provided.
Pros
MQ client application authentication and authorization.
MQ message integrity.
MQ integration with other product suites such as: IBM Websphere Application Server, Delinea Secrets PAM server, etc.
MQ error logging mechanism.
MQ APIs for .NET, Java,... based application codes.
Cons
MQ message tracking in cases of no commit or roll-back.
MQ integration with cloud based apps optimization.
MQ message data handling for testing purposes (successor of RFHUtil).
Likelihood to Recommend
IBM MQ is well established as an Enterprise Messaging Product that provides enhanced message integrity and secures message delivery to its destination, which is critical for transaction completion in the banking business. It is also followed by an experienced IBM MQ Development and support team seeking optimization of product functionality and support experience.
IBM MQ is used to expose some of our software solutions to our customers. Depending on the software and customer requirements, we offer Active/Standby or RDQM infrastructure. Our challenge is to keep the MQ Infrastructure as standard as possible to allow perfect monitoring and operability.
Pros
Resilient
Secure
Stable
Cons
PKI keystore refresh should not interrupt active channels.
AMS rules shall not be stored only on the MQ server (an admin can remove the rules to access the messages—this is exactly what we want to avoid with AMS !).
Channel name length must be improved to more than 20 characters.
Likelihood to Recommend
We often receive requests from customers to exchange files in the queues. However, the 100Mb limitation is too low, and the MQ MFT is too complicated for a point-to-point transfer.
In my organization, IBM MQ has become essential for ensuring seamless communication between data sources and my analytics platforms. Since I work directly or indirectly in data analytics and research, I rely on it to maintain the integrity and reliability of data pipelines. We use IBM MQ for real—time data integration. Our analytics process requires data from multiple sources, such as databases, APIs, and external data feeds. MQ ensures that we transfer reliably.
Pros
Ensures messages are delivered in the correct order, preventing data loss.
It provides excellent encryption and authentication to protect data during transfer.
Facilities smooth communication between diverse systems and applications.
Cons
I reckon the initial setup and configuration are complex and time-consuming.
The licensing cost is high, but the rest works fine.
The user interface could take a moment to grasp, although it is not a big challenge.
Likelihood to Recommend
It's well suited for real-time data integration in financial analytics. For example, when pulling data from multiple systems, it ensures that the data is in the correct order. This helps us maintain data integrity and perform accurate, timely analysis, which is crucial for making decisions and hence saving time.
So we are using IBM MQ to seamlessly connect different systems within our organization, ensuring reliable and secure communication. It solves the problem of integrating diverse applications, especially for critical tasks like financial transactions and cross-department workflows. This helps us maintain data consistency and improve overall efficiency across the board.
Pros
Ensures reliable message delivery across platforms.
Secure & smooth communication between various internal systems to make our work easy.
Cons
IBM MQ improve users interface for easier configuration and management. also better integration with modern cloud native technologies
Likelihood to Recommend
It is ideal for our complex environments. It is reliable and secure messaging across our system. However, sometime it is not suitable for rapid scaling.
VU
Verified User
Account Manager in Research & Development (51-200 employees)
In conjunction with App Connect Enterprise for transformation and routing of messages we are able to connect disparate systems and platforms. IBM MQ processes 1/2 billion transactions monthly without losing any data.
Pros
reliable delivery of messages even if the system goes down
provides a fast efficient mechanism for transferring data between disparate systems
works well on major business platforms (AIX, Linux, Windows, Z/OS, IBMi)
provides a method for holding messages in the case that applications are stopped
provides secure encryption of messages when transferring data
Cons
IBM MQ Explorer enhancement to allow more functionality
IBM MQ Console enhancements to allow more functionality in regards to messages (moving messages queue to queue, putting messages on a queue, copy messages to a file/queue, etc.) and in regards to defining objects (copy one definition to another and change the name of the object)
Add built-in monitoring for IBM MQ (message input rate, message output rate, % of queue depth, age of message on a queue, etc.)
Likelihood to Recommend
I have been working as an IBM MQ Administrator and IBM MQ Architect for 30 years. With IBM MQ there is no better product on the market. IBM MQ has all the functionality to meet the needs to IT in today's world. There is no better, no software more reliable, stable and expandable than IBM MQ. I have worked for major corporations dealing with trillions of dollars and other corporations dealing with processing billions of transactions monthly. This is easy for IBM MQ because it's such a robust tool. You can always go cheaper but you cannot go better.
A big retail store selling things in different places - like in their physical stores, on the internet, and from various suppliers. They had a problem because it used to takes too long to process orders and it was challenging to keep track of what they have in stock. This made customers unhappy because their orders are late, and sometimes the store runs out of the things people want to buy. As solution messagiong layer was introduced and for that IBM MQ was used to decouple the different systems involved in the order processing and inventory management process. This means that when an order is placed by a customer online or in-store, the order information is not directly processed but is instead placed in a IBM MQ message queue.
Pros
Security and Data Encryption: IBM MQ provides robust security features, including data encryption and authentication mechanisms, to protect messages during transmission.
Message Routing: It excels at routing messages to the appropriate destinations based on criteria like message content, destination availability, or message priority.
Message Transformation: IBM MQ can be used to transform messages as they move through the system. For example, it can convert messages from one format to another, such as translating XML to JSON, making it valuable for integrating different systems with varying data formats
Reliable Message Delivery: IBM MQ ensures that messages are delivered reliably and once-only, even in the presence of network failures or system crashes. It stores messages in a queue until the receiving application is ready to process them. This reliability is crucial in financial transactions, healthcare systems, and other applications where data integrity is paramount.
Cons
Cloud Integration: While IBM MQ can be used in cloud environments, more native integrations and features optimized for cloud deployments
Improved REST Support: While IBM MQ has introduced REST APIs, there may be room for improvement in terms of providing more comprehensive and RESTful integration options to align with modern microservices architectures
Open Source Ecosystem Integration: IBM MQ could enhance integration with open-source messaging technologies, such as Apache Kafka, to support a wider range of use cases and foster interoperability
Likelihood to Recommend
In the context of Internet of Things (IoT) applications, IBM MQ plays a pivotal role in managing the substantial data streams emanating from interconnected devices. Its primary function is to guarantee the dependable transmission and processing of data, catering to a diverse range of IoT use cases, including but not limited to smart city initiatives, healthcare monitoring systems, and industrial automation solutions. In the telecommunications sector, IBM MQ is employed for message routing, call detail record (CDR) processing, and network management to ensure real-time data exchange and fault tolerance. When managing the supply chain and logistics, IBM MQ is used to ensure timely and accurate communication between different entities, including suppliers, warehouses, and transportation providers. IBM MQ can be cost-prohibitive for smaller organizations due to licensing and maintenance costs. In such cases, open-source or lightweight messaging solutions may be more appropriate. For scenarios requiring extremely low-latency, real-time data exchange, and high throughput, other messaging technologies, like Apache Kafka, may be more suitable due to their specialized design for such use cases.
VU
Verified User
Consultant in Information Technology (10,001+ employees)
IBM MQ is a way of passing information between the system and the application. It is very easy to make and maintain applications in easier way. Its robust and reliable secure messaging solution is very impressive for us. Its wide range of API and language commands is very impressive. It working features of a broad range of computing platforms are also beneficial for us.
Pros
It runs on client platform so that it can easy to use.
Robust and reliable secure messaging solution.
It support a wide range of API and language.
IT control command.
Cons
Need to increase limited scalability.
Need to work on consume message in queue sometime its not worked.
Support, should be easy to reach.
Likelihood to Recommend
Message delivery guaranteed, IBM MQ supports the communication of exchange of information between the system and service via the queue. Also, they don't need to modify the existing application. Security risk while delivering the message, Performance problems sometimes it increased response rate, sometimes expected heavy use of resources.
We use the IBM MQ for our Swift message management. It has a better messaging format structure which has reduced our dispute with customers over duplicates of messages. We formally also used it on Omniflow to manage the message queuing challenge with flexcube. All tanked messages are easily worked on using IBM MQ
Pros
It better structures messages format
it prevents duplicating of messages, which is a huge thing for us
Likelihood to Recommend
I rate it 10 because the messaging formatting is good. it has reduced our issues on swift, as duplicates have been reduced as result of proper message formatting
