Server-to-Server Communication - nodejs

The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Message from discussion Server-to-Server Communication
Received-SPF: neutral (google.com: 209.85.215.50 is neither permitted nor denied by best guess record for domain of ja...@nodefly.com) client-ip=209.85.215.50;
MIME-Version: 1.0
Date: Sat, 27 Oct 2012 11:32:00 -0700
Message-ID: <CAFzK5Ef1+iMsVdkGAWBtRoUnXy_PdvKnOEG9VAuzW36AnQV...@mail.gmail.com>
Subject: Server-to-Server Communication
From: Jacob Groundwater <ja...@nodefly.com>
To: nodejs@googlegroups.com
Content-Type: multipart/alternative; boundary=bcaec539654cef7f9804cd0ea6b0

--bcaec539654cef7f9804cd0ea6b0
Content-Type: text/plain; charset=ISO-8859-1

I was wondering what others are using for communication between back-end
servers. Since I control all involved servers, I would rather not include
authentication at the application layer. Forwarding SSH ports is perfectly
acceptable.

On that note, my own research has lead me to three options, in order of
personal preference:

   1. a message queue (ZeroMQ)
   2. websockets (socket.io)
   3. synchronize against the database (MySQL or Redis)

ZeroMQ seems pretty awesome, but I am curious if anyone has tried it, and
what there experience was. For example, I stumbled across an article
discussing how their REQ/REP model can lock up
easily.<http://lucumr.pocoo.org/2012/6/26/disconnects-are-good-for-you/>
The
workaround is fairly simple, but I am interested in soliciting more
experience in the area.

Websockets seem like a "native" way, but I see them as living in the
client-server domain. For example, I would have to setup express and a
basic restful service on each back-end server. Websockets are also 1-to-1,
where as ZeroMQ supports N-to-N connections.

Synchronizing against the database would involve polling to achieve
real-time like events. I know Redis supports a pub/sub system, but does not
seem to have any RPC-like mechanisms.

In the end, I will make the decision best suited to our needs, but I am
sure I can gain from some discussion on the matter.

Thanks everyone,

- Jacob Groundwater

--bcaec539654cef7f9804cd0ea6b0
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I was wondering what others are using for communication between back-end se=
rvers. Since I control all involved servers, I would rather not include aut=
hentication at the application layer. Forwarding SSH ports is perfectly acc=
eptable.<div>
<br></div><div>On that note, my own research has lead me to three options, =
in order of personal preference:</div><div><ol><li>a message queue (ZeroMQ)=
</li><li>websockets (<a href=3D"http://socket.io">socket.io</a>)</li><li>
synchronize against the database (MySQL or Redis)</li></ol><div>ZeroMQ seem=
s pretty awesome, but I am curious if anyone has tried it, and what there e=
xperience was. For example, I stumbled across an article discussing how the=
ir <a href=3D"http://lucumr.pocoo.org/2012/6/26/disconnects-are-good-for-yo=
u/">REQ/REP model can lock up easily.</a>=A0The workaround is fairly simple=
, but I am interested in soliciting more experience in the area.</div>
</div><div><br></div><div>Websockets seem like a &quot;native&quot; way, bu=
t I see them as living in the client-server domain. For example, I would ha=
ve to setup express and a basic restful service on each back-end server. We=
bsockets are also 1-to-1, where as ZeroMQ supports N-to-N connections.</div=
>
<div><br></div><div>Synchronizing against the database would involve pollin=
g to achieve real-time like events. I know Redis supports a pub/sub system,=
 but does not seem to have any RPC-like mechanisms.</div><div><br></div>
<div>In the end, I will make the decision best=A0suited=A0to our needs, but=
 I am sure I can gain from some discussion on the matter.</div><div><br></d=
iv><div>Thanks everyone,</div><div><br></div><div>- Jacob Groundwater</div>

--bcaec539654cef7f9804cd0ea6b0--
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
Account Options
