The IBM Data Replication portfolio provides log based change data capture with transactional integrity to support big data integration and consolidation, warehousing and analytics initiatives at scale.
N/A
IBM MQ
Score 9.6 out of 10
N/A
IBM MQ (formerly WebSphere MQ and MQSeries) is messaging middleware.
IBM InfoSphere Data Replication replication allows work on the daily operation and analyzes the replicated data in real-time with no downgrade of performance. This happens thanks to the incremental data load using the log files instead of querying the database for any changes. It serves as an online backup of the database uploading the data to the cloud in real-time.
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.
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.
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.
