You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Multi-tenancy targets to share the same Blueriq solution among multiple tenants. You would typically use this when you create a Software-as-a-Service solution, where you as a service provider are in control over the infrastructure and the model.

Why use multi-tenancy?

  • Multiple customers use the same service
    • Resource sharing
    • Build once, sell multiple times

What do you need to have in place when using multi-tenancy?

  • Scaling strategy
    • When your service becomes more popular, or when it has peak usage windows, it will require more processing power. Hence, you need to scale your system to fit the service's demands
  • Tenant onboarding
    • When a new tenant will use your service, you will need to know what needs to happen to add the tenant and its users.

When not to use multi-tenancy?

  • When your services should differ for each tenant
    • More diversity between tenants leads to higher costs in maintenance, and hosting.

System requirements

The system that you require for your multi-tenant solution is 

  • No labels