IBM MQ Benefits

Sunil Sahoo
Manager at a financial services firm with 10,001+ employees
People have started using the likes of Kafka, Spark and other new messaging technologies. But when you take the likes of banks into consideration, which mostly are running on mainframes and AS/400, implementing advanced technologies are not an easy job. Getting an MQ-certified guy is not that difficult in the ASEAN market. There are a lot of certified professionals. That's one of the reasons we still use MQ for most of our messaging. We are still looking at open-source deployments but we have not yet implemented anything like that because of the knowledge GAP & dependency on the existing products. We do not have a dedicated team to take on that task yet. With IBM MQ still in the bank, and a dedicated team which has expertise in it, we really cut down the time-to-market, from a few months to a few weeks. The development framework is already there. If business comes up with requirements, technology team already know what needs to be done. And by building the in-house team, it gives us the facility where we don't need to ask the IBM guys or other vendors in the market to help us every time we have a new requirement. Another way MQ has improved the way our organization functions is customer notification. Whenever payments are happening, such as incoming payments to the bank, we need to notify the customer. With MQ we can actually do that asynchronously. There are requirements for notifying customers on a real-time base & also for each and every payment sometimes, once a day. These are be enabled with the help of MQ. In addition, there are fewer failures during the end-to-end payment process. MQ comes in very handy because we don't lose messages in transit (message persistence). It gives us the ability to store and forward messages when required. We heavily rely on MQ for these kinds of requirements. Also, we have certain applications that want to receive the messages in both production and the disaster-recovery data center at the same time. Without MQ in the picture, it would have been very difficult for us to configure that. MQ Publish subscribe capability is very helpful in that scenario. MQ has helped to reduce integration costs, mostly by acquiring the enterprise license of MQ. We can actually set up multiple MQ servers in the same environment and each MQ server is dedicated to a particular application. We also use MQ up to a level where the messages are coming from multiple host systems and they go back to a single channel. When written back, the response goes to the exact host that had sent the request (Message Affinity). Without a tool and without a messaging architecture that is as good as MQ's, it would take a lot of time in hard-coding to achieve that. Prior to the team being set up and having these frameworks in place, it took roughly two to three months to deliver any of these integrations. Now it takes three to four weeks. It has helped reduce the effort and man-hours by half. View full review »
Technical Lead at a financial services firm with 10,001+ employees
We initially went with a single server or two servers. We used a lot of the mainframe and we used it on the one server. Then we realized that we were down to a single point of failure. What we did was we enabled something called queue sharing where you have multiple landing platforms, which lets you execute multiple applications in the background. And we're now able to use our HA failover quite extensively. It previously required one server to be down and there would be an effect on customer business. Now it requires at least three servers to be down before we start feeling the workload. And even then, we're hardly ever down because we have now spread the load using the queue shared clusters. In terms of the solution helping to reduce the cost of integration, we're using what is called the MQ Appliance. Because the appliance connects multiple solutions in our bank to this platform, we don't need to procure more licenses or more servers or more infrastructure. So at the moment, we're using a very cost-effective model, compared to two to three years ago, which is when we started to consolidate servers. We had about 400 servers but we've reduced their number by moving them to the appliance. We've consolidated all of those server licenses and server infrastructures. For example, we took a server that was front-end, using Java, and connected to the mainframe. We have that entire server's application queue, entry queue, and all the objects moved onto the appliance. And there is no cost to it. It's just a box. There's no operating system on it. We have MQ on it and MQ then connects things to the rest of the bank, so we save on the infrastructure, on server licenses, and MQ licenses. We've created a setup like that a few times already in our bank. This process of integration has saved us a lot of time. Previously our projects would take at least three to four weeks. Now, once we have firewalls and security in place, and once we have an acceptable solution design in front of us, they take three to four days. From the time we design the solution until things are connected to the appliance, it takes a week. It's only fast because most of it is scripted. It's almost like a container. View full review »
Abraham Ansah-Cudjoe
Unix/Linux Systems Administrator at a financial services firm with 10,001+ employees
We have clients spread all over Africa and they have to process different types of requests, such as credit requests and debit requests. We use the Queue Manager to handle these requests. Our MQ server will accept the request and send it on to our core banking application. If you imagine the order from left to right, the application is on the left, then the enqueue server is in the middle, and the core banking is on the right. In between the enqueue server and the banking application, we have APIs and systems in place to understand the XML files. View full review »
Find out what your peers are saying about IBM MQ vs. VMware RabbitMQ and other solutions. Updated: March 2020.
406,312 professionals have used our research since 2012.
Walter Kuhn
ICT Architect at a tech services company with 51-200 employees
Most European companies have MQ, though we just added it four years ago. MQ changes the way people think about their applications. E.g., they are more integrated. We see synergies with the tool, but there is a long path to changing people‚Äôs minds. View full review »
Principal Solution Specialist at a tech services company with 1,001-5,000 employees
The on-premise installation is very valuable to us, since we are working with a lot of companies which have a very high degree of compliance. View full review »
Eduardo Cano
Architect & System Engineer at Servicio de Impuestos Internos
We use it for our factory where we have a system that uploads electronic documents for the entire country. View full review »
Pavel Shcherbukha
Team Leader of the Development Team at IBM/IT-Innovation
IBM MQ helps us scale our applications and balance our applications' performance. MQ is quite reliable. In some cases, our application became simpler and more reliable simultaneously. View full review »
Soumya Thomas
VP - Accelya Kale Solutions Ltd at Accelya World SLU
Applications are time critical, and IBM MQ has played a significant role in ensuring fast, reliable message transmissions. With IBM MQ in place, fear of messages getting lost in the case of an unplanned failure is almost none. View full review »
Alexander Fildish
Consulting BPM Architect at Ivory Software Corp
It is the most reliable product that we have ever used. View full review »
Ruud Van Zundert
MQ Engineer DevOp at ING
The product was already installed which is not surprising as it was first published around 1993. View full review »
Balanna N
Architect at Franklin Templeton
Adding concentrators was great improvement, but it lacks the SonicMQ CAA (continuous availability architecture). View full review »
It improves reliability and guarantees that messages are not lost. This is a prerequisite for the online payment process. View full review »
Jan Quist
Software Engineer at Sita
IBM MQ was found to be easy to implement and operate. It became the defacto standard, and integration problems moved from an operational issue to application solutions. View full review »
Find out what your peers are saying about IBM MQ vs. VMware RabbitMQ and other solutions. Updated: March 2020.
406,312 professionals have used our research since 2012.