Re: Hosting a Large Number of Node Apps on the IBM i

We are talking stateless here so you will never have 20.000 routing steps
to handle at the same time unless you have millions of users..

Henrik,

Maybe "routing steps" is not the right term.

All HTTP requests need to be routed to specific JavaScript functions in
Node.js.

The idea is to use URLs to "route" requests appropriately. Say a URL
pattern such as the following is used to route HTTP requests:

/major-system/module/application/requested-action

Even a moderately scope system could very well exceed 20,000 unique URLs
for more than 20,000 possible JavaScript functions (request handlers).

So maybe routing is handled with a a series of nested conditions:

When URL-major-system = "human_resources" ...
When URL-module = "payroll" ...
When URL-application = "maintain_employee_payroll_deductions" ...
When URL-requested-action = "list_employees" ...

Since you mentioned having a "stateless" environment, that raises the
likelihood of managing state for each user, and possibly for each
application identified in a URL. Wouldn't some part of the URL be used as a
key for saving and restoring user state?