Re: multi-tenant issues with stored procedures

Charles, I experienced that with the MQ broker I wrote for Cintas many
moons ago. Changing the library list was just an expensive operation, even
when I did it with an API. I believe we segregated our processes to
minimize library list switching as much as possible. But, that was a high
volume process, and I have not seen a hit from changing library lists in
lower volume processes. Maybe find a way to check the library list, and
don't change it unless necessary.

On Mon, Nov 27, 2017 at 6:55 PM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

Charles,

<vendor>

We have a proven web application architecture that supports multi-tenancy
without partitioning.

A CL command creates an "environment" for each tenant.

Each tenant has their own HTTP server instance and web portal instance via
URL sub-domain (i.e. tenant.domain.com).

Each tenant has their own set of library lists, and IFS root directory.

A CL command starts a tenant environment.

A CL command ends a tenant environment.

Every IBM i web application launched by clicking on a portal menu item
adopts the library list pertaining to that tenant.

All IBM i Jobs for each tenant run under a set of subsystems assigned to
that tenant (facilitates workload management).

We should schedule a demo.

</vendor>

In the absence of an environment like that, the fall-back appears to be
the use of IBM i partitioning, with each tenant getting their own
partition.

Most web-application architectures are distributed - web applications run
in one-to-many virtual machines and connect to a database that is running
in another virtual machine. Have you considered that?
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD