Page History
...
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.
Onboarding a new tenant means setting up a new system | Only one runtime to manage | Not currently supported by Blueriq |
Each system needs maintenance separately | Only one Blueriq software stack to maintain | |
Maintenance can be performed without other tenants noticing | Maintenance on the runtime affects all tenants | |
Easier to scale a single tenant | When the system needs to scale, you need to scale the entire system | |
Resources can be allocated per tenant. Easier to prevent noisy neighbors. | If the system experiences a sudden burst in activity, all tenants will notice this. | |
Least chance for mixing up data | Tenant data ends up in the same system, however, with proper configuration, the data is always stored in the right tenant database. |
...
Overview
Content Tools