Deploying JBoss A-MQ in a high availability (HA) environment

Slides from webinar delivered on July 16, 2013

Transcript

1. Red Hat JBoss A-MQ 6.0 Deploying JBoss A-MQ in a High Availability (HA) environment Scott Cranton July 16, 2013 – Live Webinar
2. 2 RED HAT JBOSS A-MQ Agenda • JBoss A-MQ High Availability Overview • Demonstration of a fabric-based network of fault-tolerant (master/slave) brokers
4. 4 RED HAT JBOSS A-MQ Red Hat JBoss A-MQ A small-footprint, high-performance, open source messaging platform
5. 5 RED HAT JBOSS A-MQ What is JBoss A-MQ? Open Scalable Reliable *assuming you already know it does reliable messaging
6. 6 RED HAT JBOSS A-MQ JBoss A-MQ :: Open • Open Source – Apache Software License 2.0 licensed – Based on very popular Apache ActiveMQ • Open Protocol – AMQP 1.0, MQTT, STOMP, OpenWire, … • Open Language (Polyglot) – Client native languages: Java (JMS), C/C++, .NET – STOMP clients: Ruby, JavaScript, Perl, Python, PHP, ActionScript, ...
7. 7 RED HAT JBOSS A-MQ JBoss A-MQ :: Scalable • Vertical Scaling – Only limited by I/O, compute, and I/O resources, … • Horizontal Scaling – Network of Brokers (Clustering / Federation) – Fuse Fabric (https://github.com/jboss-fuse) • Central configuration management and provisioning • Client-side discovery, load balancing, and failover
8. 8 RED HAT JBOSS A-MQ JBoss A-MQ :: Scalable Network of Brokers
9. 9 RED HAT JBOSS A-MQ JBoss A-MQ :: Reliable • Persistent Messaging – Store on File system or RDBMS – Survive restart, and process failure • Master / Slave – Lock manager – Shared Storage - SAN/GFS2 or NFS v4 or RDBMS – Replicated - Block or RDBMS replication • Managed – Red Hat Cluster Suite – Shared or Replicated storage
10. 10 RED HAT JBOSS A-MQ JBoss A-MQ :: Reliable
11. 11 RED HAT JBOSS A-MQ JBoss A-MQ :: Reliable Master / Slave – Shared Storage
12. 12 RED HAT JBOSS A-MQ JBoss A-MQ :: Reliable Master / Slave – Replicated
13. 13 RED HAT JBOSS A-MQ Fuse Fabric
14. 14 RED HAT JBOSS A-MQ Client Connection URI • Static – tcp://<host>:<port>?<connection options> – Simple, but no reconnection on failure • Failover Transport – failover:(tcp://<host>:<port>,tcp://<host>:<port>,...) – Reconnect on failure • Fabric Discovery – discovery:(fabric://<group name>) – Reconnect of failure – Coordinates with Fabric Registry
15. 15 RED HAT JBOSS A-MQ Red Hat High Availability Add-On • Smarter failure management – N+1 failover architecture – Restart on node first, then failover to back node – More sophisticated detection than just process failure • RHEL only • Complements JBoss A-MQ HA capabilities • JUDCon Boston 2013 – Resilient Messaging – http://www.jboss.org/dms/judcon/2013unitedstates/presentati ons/judcon2013_day3track3session5.pdf – http://bit.ly/18kcidy
16. 16 RED HAT JBOSS A-MQ
17. Demo Time
18. 18 RED HAT JBOSS A-MQ Demonstration Sample code and documentation https://github.com/FuseByExample/external-mq-fabric-client/
19. 19 RED HAT JBOSS A-MQ Topology
20. 20 RED HAT JBOSS A-MQ Summary • JBoss A-MQ is a highly scalable and available open source messaging product • Many HA options to meet your needs • Links – http://www.jboss.org/products/amq – https://github.com/FuseByExample/external-mq-fabric-client/ – JUDCon Boston 2013 Presentation - http://bit.ly/18kcidy