The Necessity and Pain of Moving from IBM MQ + RH Fuse to Apache Kafka + Apache Camel
summary
Compares migrating from IBM MQ with Red Hat Fuse to an Apache-based stack using Apache Kafka and Apache Camel, examining trade-offs between enterprise and open-source messaging/integration technologies. Describes doing thorough R&D on strengths, weaknesses, support and development risks, and evaluating scalability, expected load, and other criteria to choose the best solution for production environments.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:06Project goals
- 7:53Original architecture issues
- 16:56Resource problem fixes
- 22:56Platform evolution
- 26:28IBM MQ vs Kafka
- 33:45Target architecture results
- 36:55Q&A
related talks
49mHow to Finish a Migration Project? What If We Used Kafka?
42mMetamorphosis: When Kafka meets Camel
47mThe Forgotten Route: Making Apache Camel Work for You
52mConfiguring Apache Camel for the Cloud
21mHow Apache Kafka® Generates Value In Retail With Confluent
48mA Beginner's Guide to Inter-Service Messaging
51mFive years of highs and lows with Kafka
33mApache Camel 4: what to expect
