From pat@whitecrestconsulting.com  Tue Oct  3 19:57:06 2017
Return-Path: <pat@whitecrestconsulting.com>
Received: from mx.cims.nyu.edu (mx.cims.nyu.edu [128.122.49.99])
	by mail.cims.nyu.edu (8.15.1+Sun/8.15.1) with ESMTP id v93Nv69e003007
	for <shasha@mail.cims.nyu.edu>; Tue, 3 Oct 2017 19:57:06 -0400 (EDT)
Received: from mail-qt0-f181.google.com (mail-qt0-f181.google.com [209.85.216.181])
	by mx.cims.nyu.edu (8.15.1+Sun/8.15.1) with ESMTP id v93Nv483019335
	for <shasha@courant.nyu.edu>; Tue, 3 Oct 2017 19:57:04 -0400 (EDT)
Received: by mail-qt0-f181.google.com with SMTP id 6so7143374qtw.3
        for <shasha@courant.nyu.edu>; Tue, 03 Oct 2017 16:57:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=whitecrestconsulting-com.20150623.gappssmtp.com; s=20150623;
        h=mime-version:subject:from:in-reply-to:date:cc
         :content-transfer-encoding:message-id:references:to;
        bh=Z0o5yvO7DKRa7mChzaneWuXcbD61qkRoxgNRjtoB3go=;
        b=akNe9gm6hfMtYjag+i5GDRpNCBlJOI1Wu7YpBAKNKtxaYmHZIoaQQ8iMEcvNbzCOY6
         25CPmrnOAhYaJ7YVXAls7leOOO/Y72q7+3zdCGKx3gzuNTjg2ZY8sIjPfx8TLNQiKk4A
         syk27Ud4fj0Vc9Nx9yBkBy41vLVdbrCQAnEebjUYCQVza0oYXETSqslexG15IxLKLkIp
         Wcw/TgUpST9GIjZI6UzLf+6uE1TK8z+E42hl6N4ltx5oDdOmmUCaHBHCDFF5x9qnpJJ6
         I8SGDR1qwzw+kFLgn+p8XkhgKnEp2sGAOM1CGXk0URThPdTbG0TgbYQ2CJAURSPCpRFY
         mwvQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc
         :content-transfer-encoding:message-id:references:to;
        bh=Z0o5yvO7DKRa7mChzaneWuXcbD61qkRoxgNRjtoB3go=;
        b=qSxCvqscuDBHPzT6DbQg8+zCX0f1myTRqAezLOwUowOasbDeDtM/cT0dR67fd525h8
         jP4DMtSnRSvan1DVd20MuxQ2V1ROAlO52xxTIqkScqWKcSkzTfBMbLCovvQWB/rPWspY
         hc1rUvtLrd66HjoIRYr3qUX2NcPqZFcQTtDNzpc4DzhANXrOoSO8e4Tsa+E5tHQxkXcE
         awcU8vNddWjR9lPNNrD6aZIvDORskzOLrPDNCCEtWAHxG3NwUTqICwImRjtn2bEU3QxF
         l3EfgdXB+DLLgnzxp7u1d5m1/Yz0uOizDkFL7KxVRGtk/rPgUYQ29WjlJqHVpxfUAYbP
         QSJg==
X-Gm-Message-State: AMCzsaVXZPj0hEOVGHL21c0Q8sW0gJ6FdYU04PGMvflRjk7KieCYrb0Y
	AvUERccIQCYuVIcxpIM3ESCSVM4Lo+G9
X-Google-Smtp-Source: AOwi7QAYrjMVftvvBf1n58Fekrznefn+L3zEtldc2xQq9IYnCbLKt0iyPt+49krEONmMS+Wlyr5m8Q==
X-Received: by 10.200.8.131 with SMTP id v3mr16925310qth.262.1507075019172;
        Tue, 03 Oct 2017 16:56:59 -0700 (PDT)
Received: from ?IPv6:2600:380:bd6a:acef:a8f0:9cc3:a45b:eb84? ([2600:380:bd6a:acef:a8f0:9cc3:a45b:eb84])
        by smtp.gmail.com with ESMTPSA id p64sm9014098qkb.47.2017.10.03.16.56.57
        (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Tue, 03 Oct 2017 16:56:58 -0700 (PDT)
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (1.0)
Subject: Re: explanation of brokered messaging vs. brokerless messaging
From: Pat DeFrancesco <pat@whitecrestconsulting.com>
X-Mailer: iPhone Mail (15A402)
In-Reply-To: <201710032338.v93NcApF026647@linax2.cims.nyu.edu>
Date: Tue, 3 Oct 2017 19:56:53 -0400
Cc: shasha@courant.nyu.edu, sam.mao@7-chord.com, roy.lowrance@gmail.com,
        kristina.fan@7-chord.com, gokul.chebiyam@7-chord.com
Content-Transfer-Encoding: quoted-printable
Message-Id: <DE7624B0-B1FA-4E94-9943-76E76707045C@whitecrestconsulting.com>
References: <CAKYmtHOv8=14dFo1e0nEjjwNbbe2DfZz9nCKXe81UxUdMaYCoQ@mail.gmail.com> <201710032338.v93NcApF026647@linax2.cims.nyu.edu>
To: Dennis Shasha <shasha@cims.nyu.edu>
X-Greylist: inspected by milter-greylist-4.6.2 (mx.cims.nyu.edu [128.122.49.99]); Tue, 03 Oct 2017 19:57:04 -0400 (EDT) for IP:'209.85.216.181' DOMAIN:'mail-qt0-f181.google.com' HELO:'mail-qt0-f181.google.com' FROM:'pat@whitecrestconsulting.com' RCPT:''
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (mx.cims.nyu.edu [128.122.49.99]); Tue, 03 Oct 2017 19:57:04 -0400 (EDT)
X-Virus-Scanned: clamav-milter 0.99.2 at mx
X-Virus-Status: Clean
X-Scanned-By: MIMEDefang 2.80 on 128.122.49.99
Status: R

I spoke with a messaging architect following our meeting today (Pari for tho=
se who know her), who has worked directly with RabbitMQ, ZeroMQ, Aeron, and L=
BM / 29 West (strike LBM because it costs a fortune, though the co-founder o=
f Aeron was the founder of LBM, who I couldn=E2=80=99t remember this afterno=
on, along with the LMAX CTO).

Without hesitation Pari said RabbitMQ for this environment, for the followin=
g reasons:

- Easiest to integrate to with minimal dev resources, less configuration and=
 custom dev work.

- RabbitMQ has strong integration / support for Python.

- No need to build custom resilience / persistence (needed for ZMQ, packaged=
 with Aeron).

- TCP friendly, eliminating the need to configure and deal with multicast, r=
educing complexity.

- Strong support community, whereas ZeroMQ had tailed off / was less active i=
n last year, and Aeron has light support for Python - much stronger and acti=
ve development for Java and C++.

- Easiest messaging protocol to the transition away from if needed.

Speed will be a trade off, but I don=E2=80=99t think micros or nanos are in s=
cope for initial MVP, and can transition to a more latency sensitive archite=
cture on the future.

Based on this my vote is RabbitMQ for now, with consideration for Aeron in t=
he future. =20

Roy - 20 hours to spare!  What to do with all the free time?!

Pat

Patrick M. DeFrancesco
+1 860 978 2236

> On Oct 3, 2017, at 7:38 PM, Dennis Shasha <shasha@cims.nyu.edu> wrote:
>=20
> I'm a big fan of zeromq. Extremely robust and fast.
>=20
> Roy Lowrance <roy.lowrance@gmail.com> wrote:
>=20
>> This support Pat's point from this afternoon: zeromq has the abiity to be=

>> faster than RabbitMQ.
>>=20
>> http://zeromq.org/whitepapers:brokerless
>>=20
>> Roy Lowrance
>> tel: +1 347 255 2544
>=20

