Re: Using Node w/ Apache -- WEB400

Hi Aaron

No this version of the framework is our platform agnostic version. We still use the good old RPG version on the IBMi.

Having said that I did set up the node version up on one of our LPARs (with Redis) and although it worked the performance was awful. I narrowed it down to redis being the issue but I didn't get as far as finding out why it performed so badly.

Cheers
Kevin

On 16 Dec 2016, at 19:27, Aaron Bartell <aaronbartell@xxxxxxxxx> wrote:

Kevin, are you using Redis on IBM i?

Aaron Bartell
IBM i hosting, starting at $157/month. litmis.com/spaces

On Fri, Dec 16, 2016 at 1:01 PM, Kevin Turner <
kevin.turner@xxxxxxxxxxxxxxxxxxxx> wrote:

Hi Nathan

It's configurable in our setup, so you could have one queue for everything
or one queue per app or one per functional area or even one per module
etc. The number of processes waiting for arrivals on each queue is also
variable and it scales up and down on demand. It's very much like the sort
of thing you can do with data queues. We find redis is faster than using a
reverse proxy but it is similar from a topology point of view. On the
backend the process loads the module on demand (with require) and then
hands off the data for it to do its thing.

Cheers
Kevin

[https://www.netcracker.com/assets/img/netcracker-social-final.png] ƕ
On 16 Dec 2016, at 18:30, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

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?
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing

list

To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.

________________________________
The information transmitted herein is intended only for the person or
entity to which it is addressed and may contain confidential, proprietary
and/or privileged material. Any review, retransmission, dissemination or
other use of, or taking of any action in reliance upon, this information by
persons or entities other than the intended recipient is prohibited. If you
received this in error, please contact the sender and delete the material
from any computer.
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.

--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.

________________________________
The information transmitted herein is intended only for the person or entity to which it is addressed and may contain confidential, proprietary and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.