A completely separate node.js process that knows nothing about HTTP picks
the request off the redis queue and hands it off to the node.js module that
is supposed to deal with it.


Thanks for your reply, Kevin. Having one Node process listening on an HTTP
port, then forwarding requests to another Node process listening on a Redis
queue seems comparable to a reverse proxy redirecting requests to another
HTTP server. In both cases, you're using sockets to send and receive
messages. Except in your case, you're using a 3rd party message
broker(Redis) to serialize requests in FIFO order.

In regards to the external Node process (the one that implements a BusMQ
interface with Redis), do you implement one of those per application? Or do
you implement one of those processes for a large number of applications,
and dispatch requests to in-process JavaScript modules?

The sample module interface you shared suggested the latter. But you didn't
say explicitly. Thoughts?

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.