Presented by Justin Reock, CTO at DX

When production reliability is on the line, your message broker can’t be the weak link. In this recorded deep-dive, Justin Reock cuts through configuration sprawl to focus on the patterns that actually prevent message loss.

Whether you are standing up a new instance or stabilizing an existing one, this session provides a blueprint for mapping JMS fundamentals to durable behavior, choosing the right persistence strategy, and implementing high-availability that survives real-world outages.

In this recorded session, you’ll learn how to:

• Refresh the Essentials: Revisit the JMS/ActiveMQ basics that dictate durability (providers, producers/consumers, and queues vs. topics).
• Apply Durability Patterns: Master topic/queue retention, durable subscribers, and virtual topics for scalable distribution.
• Optimize Persistence: Navigate KahaDB maintenance vs. JDBC, and identify exactly when persistence is—or isn’t—required.
• Implement HA Topologies: Deploy shared-store KahaDB master/slave setups, networks of brokers, and robust client failover semantics.
• Avoid Common Pitfalls: See a live failure simulation that highlights the top misconfigurations causing message loss.

Walk away with a pragmatic checklist for production rollouts and a clear strategy for keeping your messaging tier resilient through upgrades and failures.