Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 92989 invoked from network); 5 Feb 2010 20:36:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 5 Feb 2010 20:36:07 -0000 Received: (qmail 68652 invoked by uid 500); 5 Feb 2010 20:36:07 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 68590 invoked by uid 500); 5 Feb 2010 20:36:07 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 68580 invoked by uid 99); 5 Feb 2010 20:36:07 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Feb 2010 20:36:07 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Feb 2010 20:35:59 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1NdUtu-0002ZM-1v for users@activemq.apache.org; Fri, 05 Feb 2010 12:35:38 -0800 Message-ID: <27473571.post@talk.nabble.com> Date: Fri, 5 Feb 2010 12:35:38 -0800 (PST) From: boday To: users@activemq.apache.org Subject: clustering options for HA and horizontal scalability MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: boday@vektrel.com I'm trying to determine my options for clustering my AMQ 5.3 application that uses ServiceMix 3.3.1 and Camel 2.1. I'm performing high volume message processing and I need to cluster for high availability and horizontal scalability. Here is basically what my application does (using Apache Camel)...HTTP->QUEUE->PROCESS->DATABASE->TOPIC So, I've read all the ActiveMQ and ServiceMix clustering pages, but am still not sure what to do. I know I can use a Master/Slave setup for HA, but that doesn't help with scalability. I've read about network of brokers, but am not sure how this applies to my application. For example, if I deploy identical Camel components on multiple nodes in a cluster, how will the nodes "interact" exactly? If I point my HTTP producer at one node (NodeA), which messages will get sent to NodeB? Will the queues/topics be shared between Node A/B...if so how, are messages split or duplicated? Also, how would an external client subscribe to my "outboundTopic" exactly (and get all messages, etc)? Alternatively, I've been thinking that I should just share a single AMQ broker between multiple ServiceMix instances. That would be cleaner in that there would only be one set of queues/topics to manage and I could scale by adding more instances. But, now I'm limited to the vertical scalability of a single broker and I'm back to a single point of failure... If anyone can clarify the trade-offs for me...I'd appreciate it. Also, I posted this on the Camel forum as well...not sure where it best fits http://old.nabble.com/clustering-Camel-with-AMQ-ServiceMix-td27462441s22882.html ----- Ben - Senior Consultant using SMX 3.3.1/Camel 2.1 -- View this message in context: http://old.nabble.com/clustering-options-for-HA-and-horizontal-scalability-tp27473571p27473571.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.