IBM’s App Connect is a cloud-based data integration platform with data mapping and transformation capabilities within connectors between high-volume systems. App Connect also offers near-real time data synchronization and an API builder that is adaptable to the user’s coding skill level.
N/A
IBM MQ
Score 9.0 out of 10
N/A
IBM MQ (formerly WebSphere MQ and MQSeries) is messaging middleware.
N/A
Pricing
IBM App Connect
IBM MQ
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
IBM App Connect
IBM MQ
Free Trial
Yes
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
IBM App Connect
IBM MQ
Considered Both Products
IBM App Connect
Verified User
Anonymous
Chose IBM App Connect
We selected IBM App Connect Enterprise due to our confidence in IBM as a long-term partner and our history with their integration technology (Message Broker/Bus). IBM App Connect provides the robustness and high reliability needed for our core on-premises systems, with proven …
The choice of IBM App Connect was a strategic decision driven by the urgent need for agile, user-friendly, and cost-effective application and data integration. While DataPower, webMethods, and API Connect are powerful tools in their own rights, their primary focuses as security …
IBM App Connect started as MQSeries Integrator (MQSI) more than 20 years ago. In the IT environment, this is like an eternity. And this allowed a lot of customer experience and needs to be embedded in the product. Without it becoming a legacy application. The changes done in …
I used the IBM WebSphere DataStage tool which is an ETL tool where we extract transform and load. This tool is a little tougher to understand than App Connect. For example, to build a job in App Connect is easier than DataStage. We can schedule the job to run in the same …
IBM API Connect is positioned ahead of Apigee in the Gartner report. But in my opinion the development experience and the data transformation capability is way better in Apigee and it’s a proved solution and has a huge client list. (I have worked on an American Express …
We did not select Cast Iron as our iPaaS solution, it was the weakest competitor in the field that we evaluated. Our experience was that it was not nearly as easy to learn, without in-depth training and guidance, and the developer UI was extremely buggy. We subjected each of …
WebSphereCast Iron is preferred for our sales and delivery teams over Informatica. We find the products and teams for WebSphere Cast Iron easier to work with here and find WebSphere Cast Iron better when integrating with non-Salesforce systems. WebSphere Cast Iron struggles to …
Application Integration and Middleware Solution Certified Specialist
Chose IBM MQ
IBM MQ meets enterprise messaging business needs in terms of platform stability, functionality, support, and the list of APIs provided for client app integration, while Rabbit MQ is not an enterprise messaging platform but rather an open-source broker for point-to-point …
I've also used Apache Kafka and RabbitMQ. Compared to these, IBM MQ offers superior reliability and transactional integrity, making it a better choice for complex, mission-critical enterprise environments where message delivery and security are paramount. We chose IBM MQ for …
Kafka is renowned for its impressive throughput, fault tolerance, and real-time data streaming capabilities. Nonetheless, IBM MQ remains the preferred choice due to its unwavering commitment to guaranteed delivery and exceptional reliability. Fault-Tolerant Architectures of IBM …
Apache Kafka may be a better option in comparison with IBM MQ its real-time data streaming and large data payload service. It depends upon the specific requirement and meets those needs. MuleSoft any point platform is very easy to connect to various other types of platforms in …
Both are useful in their own right and we actually use IBM MQ together with PCWP. IBM MQ automates our tasks and saves a lot of tedious work we would otherwise have to do manually.
The product are really similar, basically it depends on where is your infrastructure and your project goals, but talking about this specific product, if your architecture team makes a good design, IBM MQ should do the work and will provide your systems with the capabilities …
I've used Tibco Software. I've found IBM MQ more simplified than these with a good community allowing everyone to quickly learn and understand the various mechanisms.
We found IBM MQ very easy to get started and quick to learn by the new users with a short learning curve and seamlessly integrates with IBM products, and quick to perform self-service analytics and make informed business decisions. IBM MQ is also very straightforward in …
The functionalities on IBM MQ are more responsive and functional unlike the above platforms and the training when you are new to IBM MQ is very effective and not much time wasted to become a Pro. The interface security setting and the adjustment of all the features capabilities …
I have not used similarly featured products in the company. The services that we have received from this platform have always been the best. The troubleshooting models ensure that data flow across the applications is not affected by any external effects, enhancing daily …
IBM MQ is a leading competitor in this type of software. We are very happy at my organization to be using IBM MQ. It has a great, easy to use interface that works more seamlessly compared to the competitors out there. IBM MQ also seems to offer the best level of security which …
IBM MQ is very stable and a proven product compared to other Messaging platforms available. Performance was better than WSO2 product and also the RabbitMQ. Though Kafka and IBM MQ is not directly comparable, Kafka is more suited for event based systems and also where there is …
IBM MQ is the powerhouse but has a price, while ActiveMQ is free and get things done. If the project warrants it, the use of IBM MQ is highly recommended. But if the project does not need the power, it is better to avoid the cost.
I tested/used TIBCO EMS which is built for a proprietary platform. It is focused on providing a messaging platform with TIBCO, therefore in that particular case IBM MQ was ´*not* used, because of the deep integration between TIBCO products. Also tried/evaluated ActiveMQ but it …
[We selected] IBM MQ [because it] will help in processing all the transactions. Fail over transactions can be processed. [It allows us to] track of all the transactions. IBM MQ is the best for all the batch transactions.
We recently changed or migrated to IBM MQ from SONIC MQ and we have zero or negligible message loss. Clusters architecture in IBM MQ is way faster and simpler to understand.
IBM App Connect is well-suited to serve as a central integration hub, particularly for scenarios involving data transformation, complex routing logic, and dynamic backend routing. It excels at enabling legacy system modernization and supports real-time, event-driven architectures effectively. However, it is less appropriate for simple point-to-point integrations or for use cases requiring workflow process management and human task orchestration, where BPM or lightweight automation tools may be more suitable.
As we have critical data such as payments which needs to be managed across a number of platforms.
MQ ensures guaranteed delivery of this data.
Setting up a new application to use MQ is a relatively simple process.
To track data both internally and externally you can set MQ up to send back acknowledgement . Very useful if one party say they have not received some data.
Not suited.
If an application has a requirement to get information from a database without any concerns of losing data . Using JDBC connecting directly to the database can reduces the number of jumps the application needs to make to get to the database.
If an application wants to store information and then send as a large batch file it is not recommended to use MQ. MQ applications should be used for data which needs to be sent immediately. MFT (MQ file transfer) however can utilise MQ for file transfers
The documentation is very clear,It is understandable and the support helps to configure it in the best way.
Server guidelines make it possible to get the most out of work management. It's broad, we can work with different operating systems, I really recommend using linux.
It is highly compatible with systems, brockers, applications, and data accumulation programs, it is possible to configure everything so that after the installation of programs, they can communicate with each other and then throw data to an external program that accumulates it and represents in clear details of steps to follow and make business decisions.
I can only speak wonders about the program; I think it is a program with enough serious track record to meet the company's expectations. However, it should be noted that I could suggest that promotional packages be made from time to time for those of us who are already clients of more than one year.
In every sense, the program fulfills what it promises, which is to generate a good connection and cohesion of programs to be able to make commitments between them.
It is the best on-premise application to cloud integration in the market. I guess IBM is planning to integrate IBM App Connect with the IBM API Connect solution.
You can do some really powerful things with this system. The overall design is an attempt to make configurable some of the routine tasks/common functionality, but allow for development/customization of the core of the application.
I give it a nine because it has significantly improved my team's data reliability and operational efficiency. Its great security features give us peace of mind, knowing our sensitive data is well protected. While the setup might initially be complex, I believe the long-term benefits far outweigh this hurdle.
As I have said before, the program is stable; I think that is the great reason why it has been maintained for years and days in the company; despite the hard use that we have given it, it has behaved well during both day and night shifts.
The IBM Support team has offered unmatched insight. Their personnel helped us actualize several things that seemed impossible before. You see, previously we would develop a software solution, but it would take months before rolling it out mostly because we had further build additional specific interfaces. The support team suggested we procure App Connect alongside MQ. Right now, we just hop into the IBM MQ platform, connect the software with AppConnect, and a few modifications are done, then it's ready within a few days.
We selected IBM App Connect Enterprise due to our confidence in IBM as a long-term partner and our history with their integration technology (Message Broker/Bus). IBM App Connect provides the robustness and high reliability needed for our core on-premises systems, with proven scalability to the cloud. Its key strength is enabling deep integration by combining low-code with the power of complex, custom logic, ensuring the platform's capabilities exactly matched our need to handle complex flows.
Kafka is renowned for its impressive throughput, fault tolerance, and real-time data streaming capabilities. Nonetheless, IBM MQ remains the preferred choice due to its unwavering commitment to guaranteed delivery and exceptional reliability. Fault-Tolerant Architectures of IBM MQ which allows active-standby queue managers, to build fault-tolerant architectures that ensure continuity of service in the event of hardware or software failures.