Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

One very important aspect in a multi-tenant is data separation. Persistent data for one tenant should under no circumstances be shared with other tenants. The image below lists strategies on how a multi-tenant system can be set up. Blueriq doesn't support the third strategy. When you are creating the solution architecture for your multi-tenant solution, you should consider the trade-offs that each strategy has.

Image Modified

(minus) Onboarding a new tenant means setting up a new system(plus) Only one runtime to manageNot currently supported by Blueriq

(minus) Each system needs maintenance separately(plus) Only one Blueriq software stack to maintain
(plus) Maintenance can be performed without other tenants noticing(minus) Maintenance on the runtime affects all tenants
(plus) Easier to scale a single tenant(minus) When the system needs to scale, you need to scale the entire system
(plus) Resources can be allocated per tenant. Easier to prevent noisy neighbors.(minus) If the system experiences a sudden burst in activity, all tenants will notice this.
(plus) Least chance for mixing up data(minus) Tenant data ends up in the same system, however, with proper configuration, the data is always stored in the right tenant database.

...