Return-Path: X-Original-To: apmail-activemq-users-archive@www.apache.org Delivered-To: apmail-activemq-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9DE8510635 for ; Thu, 15 Aug 2013 18:00:29 +0000 (UTC) Received: (qmail 58762 invoked by uid 500); 15 Aug 2013 17:46:52 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 58629 invoked by uid 500); 15 Aug 2013 17:46:40 -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 58309 invoked by uid 99); 15 Aug 2013 17:46:20 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Aug 2013 17:46:20 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of christian.posta@gmail.com designates 209.85.217.182 as permitted sender) Received: from [209.85.217.182] (HELO mail-lb0-f182.google.com) (209.85.217.182) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Aug 2013 17:46:12 +0000 Received: by mail-lb0-f182.google.com with SMTP id v20so871088lbc.27 for ; Thu, 15 Aug 2013 10:45:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=tcTGLzcVKbZ5kNhmSjmvJd/4hCCOewd4LCqeIX4WRgc=; b=zQSmL1rBKwicVEoLF/vSSuLPugjq5RGM5hB2h2t2xNFc4V+FrK/R9pfgU60zTPUysb 3AmleTJTyN9lxdwoez9Gl/4n8E6h12JJfVmZdn54jGgpUYYmGxSpHdFzEJBC7+AHRTpO t4TO6UFQR9zz+sIQqnkz5kDSm6gbQu8izCask6joGKS7V0TPDtboPuv7bUSgiR3nLgVV mEY8y2Exo/fXVP0tiKOzJ5rNes9NzhCwqdAbmTJXH38ZxNY9sFd8SF+xGYGyWrLHTctn /PPcmhU+XT9YN6U++oLDz6a2mjfEsyyxJVi6RA719eB0R70r3eS34QQh05kYZy3QElL0 u/bg== MIME-Version: 1.0 X-Received: by 10.112.29.17 with SMTP id f17mr1313463lbh.45.1376588751611; Thu, 15 Aug 2013 10:45:51 -0700 (PDT) Received: by 10.114.2.239 with HTTP; Thu, 15 Aug 2013 10:45:51 -0700 (PDT) In-Reply-To: References: Date: Thu, 15 Aug 2013 10:45:51 -0700 Message-ID: Subject: Re: Apache Apollo Limit Topics From: Christian Posta To: "users@activemq.apache.org" Content-Type: multipart/alternative; boundary=001a1133c6908ab04504e4000b1b X-Virus-Checked: Checked by ClamAV on apache.org --001a1133c6908ab04504e4000b1b Content-Type: text/plain; charset=ISO-8859-1 Well, Apollo was built to be able to sustain large numbers of destinations. But don't take it from us, if I were you I would take a look here: https://github.com/chirino/mqtt-benchmark and run a benchmark to be sure. On Thu, Aug 15, 2013 at 8:12 AM, Leonardo Bragatti wrote: > Hi everybody, > First of all, thanks for let me joining the group > > Someone can help me with the following question: > I'm using the MQTT Protocol to manage the message between my applications > The device connect to server and create a dsub, and this dsub is the > consumer of the topics > The topics refer to database models > We're planning to create the topics in the following structure: > domain.com/account/app/model/model_id > But our concern is that the server will not overload by having to manage so > many topics > > What people do you think? > > -- > Regards, > Leonardo > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta --001a1133c6908ab04504e4000b1b--