Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 60202 invoked from network); 23 Oct 2008 12:12:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 23 Oct 2008 12:12:45 -0000 Received: (qmail 58711 invoked by uid 500); 23 Oct 2008 12:12:47 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 58699 invoked by uid 500); 23 Oct 2008 12:12:47 -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 58688 invoked by uid 99); 23 Oct 2008 12:12:47 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Oct 2008 05:12:47 -0700 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG 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; Thu, 23 Oct 2008 12:11:33 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1Ksz2x-00050S-Uv for users@activemq.apache.org; Thu, 23 Oct 2008 05:12:11 -0700 Message-ID: <20129668.post@talk.nabble.com> Date: Thu, 23 Oct 2008 05:12:11 -0700 (PDT) From: Maarten_D To: users@activemq.apache.org Subject: Add simple service registry to ActiveMQ MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: maarten.dirkse@gmail.com X-Virus-Checked: Checked by ClamAV on apache.org Hi, I'm developing a distributed system that has four types of components that need to work together. At first I just had a simple configuration with 1 component of each type, working and wired together using ActiveMQ. I now want to expand the system to include multiple components of each type and support dynamic adding/removing of components. Since the exact topography of the component network can't be known in advance, I need some sort of component discovery mechanism. Let me give a concrete example: Component A generates messages that need to be processed by component B. Right now, component A knows where to find component B because it has the queue name hardwired into its configuration. I want to develop a system where component A and B can both be started unawares of each other, and component B can then somehow discover the queue that component A puts its messages on, and start consuming. That way I could deploy 100 instances of component B, and not have to do any configuration: they would all know where to find work. So now my question: what is the best way to add this sort of service discovery mechanism to ActiveMQ? I've looked at ServiceMix, which supports service discovery, but moving to a full-blown ESB just for one feature seems like overkill. I've also looked at jUDDI, but that seems to be very web services specific. Of course it would be fairly easy to implement a trivial service discovery mechanism using just JMS, but I don't want to do the work unless I really have to. Does anyone know of a good solution to this problem? Regards, Maarten -- View this message in context: http://www.nabble.com/Add-simple-service-registry-to-ActiveMQ-tp20129668p20129668.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.