Replacing legacy message queueing solutions with RabbitMQ
summary
Claims ability to replace old brokers like DEC Message Q by implementing a drop-in replacement API that mirrors the original functions and return codes and sits on top of the RabbitMQ C client. Uses RPC for the name service, RabbitMQ streams for journaling, maps numeric queue IDs to names, and accepts limitations like no content‑based consumption. Achieves about 80–95% feature parity, deployed for a US customer and proves effective with COBOL/Fortran legacy apps.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 3:12Message queuing history
- 8:28RabbitMQ with Cobalt
- 13:24Deck Q replacement
- 19:44Modern queuing benefits
- 22:56Q&A
related talks
16mTo queue or not to queue, that is the question.
47mEverything Loosely Coupled - Advanced Integration Patterns and Their Trade-Offs
41mDesign (Failures) Case Study
55mCode the future, now
52mA C++ MQTT Message Broker for the Enterprise
01h 19mBackporting C++ Safety
40mPrincipals of System Integration
35mLegacy Monolith to Microservices