The easiest route - we'll conduct a 15 minute phone interview and write up the review for you.
Use our online form to submit your review. It's quick and you can post anonymously.
My main use case for IBM MQ is its integration with APIs, and what we do is have a workflow system. In order to trigger the workflow, which is more of an asynchronous processing, we send a message to the workflow through IBM MQ, where the workflow listens to the IBM MQ message and then starts creating the case in the workflow system.
The best features IBM MQ offers are the topic and subscription, as well as the IBM MQ session and message rollbacks, especially for JMS integration. IBM MQ serves as the underlying foundation for our JMS messages.
IBM MQ has positively impacted my organization by enabling asynchronous processing, which means we do not need to wait for any responses from our downstream systems.
IBM MQ can be improved by having a feature where a message can be rolled back, especially if I want to go back to a particular message.
I have been using IBM MQ for around ten years, including five years and another five years.
IBM MQ is stable.
IBM MQ's scalability is very good; we have clusters in place, so we are satisfied with its performance.
Before choosing IBM MQ, I did not evaluate other options.
I would rate IBM MQ a nine out of ten; it is an excellent product, but it requires more additional features similar to Kafka. I would advise others looking into using IBM MQ to consider it as the best product for asynchronous data communication between systems.
My main use cases for IBM WebSphere Application Server are mostly web-oriented, involving Servlets, core Servlets, and Beans, which includes my personal projects.
The use cases for IBM MQ in my context involve working in tandem with WebSphere, where data is taken based on events. I notice that people are increasingly moving towards Kafka, especially here, as it performs similar functions to IBM MQ.
In my opinion, the best features of the WebSphere Application Server make it the ultimate product. There is nothing higher than WebSphere. The market has Tomcat, JBoss, and other low-level application servers, but then there is WebSphere. I prefer WebSphere particularly on AIX because it's a very powerful engine. AIX is a powerful engine, and I don't think there is any UNIX system which is better than AIX. I'm 100% confident about that. I have been working with AIX since my time as an IBMer in Europe and also here in the Royal Bank, where we have a huge forest of AIX machines, running WebSphere on many of them. I also have experience with WebSphere in Windows, which is also very good; from an administrative and development point of view, it's transparent. There is not much worry about having WebSphere on AIX or Windows.
I would assess the integration of WebSphere with third-party tools and services in terms of modernizing the IT infrastructure as very good. I was involved in an application where I integrated WebSphere with Node.js and also with Blue Prism. I executed many REST applications because at my core I am a developer. Although my title is architect, I am still a geek and a developer, and I started as a developer, so I carry that passion with me.
At the Royal Bank, I have benefited from WebSphere's high availability and clustering because the overwhelming majority of our environments are clustered with IBM HTTP Server in front. We have clusters not just with two WebSphere engines; some of them even have four or six WebSphere engines, all managed under IBM HTTP Server. Everything is federated.
From my perspective on the best features of IBM MQ, if given the choice between Kafka and IBM MQ, I would choose IBM MQ as it is by far the best. However, people opt for Kafka because it is open source and comes at no cost. This conveys my mantra that the best solution doesn't always align with being the right one, highlighting the significant difference between the best and the right.
Regarding the improvement of the WebSphere Application Server, WebSphere is at version 9.0.5.23, and last month they released another fix because they periodically put out fixes. Previously, there were very frequent version increases, but now they maintain the focus on 9.0.5 and its different releases. Oracle announced that 2030 will be the last year when Java 1.8.x will be supported, which raises questions about the future of WebSphere since it is based on Java J2EE 7 and Java SDK 1.8. I wonder what the future holds for WebSphere after 2030 since I have never seen any communication from IBM detailing this trajectory.
I have around eight years of experience with IBM products in general, as I was working with IBM Eastern Europe in Vienna before coming to Canada, and I worked with WebSphere, OS, even OS operating system, AS/400. At that time, it wasn't I5, I6; the name was AS/400. After coming to Canada in January 1998, I worked with IBM Canada in Steeles, Toronto, until 2002.
I would rate the support from IBM for their WebSphere Application Server as very good, although I have only called IBM for support two or three times in my life. Most of the time, I figure things out myself, so I would rate it a 10, with 10 being the best.
For IBM MQ support, I have only contacted support once in my life, and the experience was very good, so I can't complain. I would rate it a 10.
Positive
In my opinion, the initial setup of the WebSphere Application Server is not complex at all. I have been working with WebSphere since my time in Romania as part of IBM in Vienna, and now it is straightforward for me. While it might seem challenging at the beginning, once you get your hands on it, it becomes very straightforward.
The price of the WebSphere Application Server at the Royal Bank is influenced by our unique agreements with IBM, as it's a large establishment with numerous IBM products, including mainframes. I am not aware of the specific agreements, but it is similar to purchasing in bulk, where the pricing structure is not the same as buying a single item at a grocery store.
I still use IBM WebSphere Application Server, specifically the latest version which is 9.0.5, and I work with IBM MQ and Rational as well.
I have not had any experience with AppScan or other testing tools; I am not utilizing any tools besides Rational.
I have used management tools with IBM MQ, and I find them beneficial for optimizing message flows. I utilize these tools, but often rely on my instinct, as IBM MQ is built on Java, which I have extensive experience with.
Regarding high availability with IBM MQ, we also have IBM MQ in clusters. Having IBM MQ in a cluster is useful since the cluster setup means we have some form of high availability.
I rate this solution 10 out of 10.
