Question
Anthem Insurance Companies
US
Last activity: 12 Mar 2020 7:02 EDT
Multitenancy - Data Isolation
I have a requirement to scale the application to accommodate multiple LOBs. I am inclined to use Pega Multitenant approach.
I would like to know if the “Data Isolation” can be achieved by having “PegaData” for each tenant.
I understand, to prevent data “Cross Talk”, there is a tenant ID associated for each tenant. This is just to avoid cross talk but ideally the customers would prefer to have their own Database/Schema.
I appreciate your response.
Pegasystems Inc.
US
Wouldn't the different LOBs want their own database?
Ideally those LOBs would share a common codebase.
You do not need multi-tenancy for that.
The users of the hosted applications belong to the same parent Org ?
Anthem Insurance Companies
US
Wouldn't the different LOBs want their own database? - Yes, every LOB wants their own Database.
Ideally those LOBs would share a common codebase. - I agree, We can have Common PegaRules.
You do not need multi-tenancy for that. - What are the other options ?
The users of the hosted applications belong to the same parent Org ? - No they are different organization.
Pegasystems Inc.
US
If every LOB wants there own database you can define a different cluster for each LOB, orchestrating that cluster using technologies such as kubernetes (open source) or OpenShift (IBM/Red Hat).
In a cloud environment you can also leverage the cloud vendor's way of providing "elasticity". Pega supports, and will continue to support, cloud choice.
FYI: There is a kubernetes work group exploring multi-tenancy.
Anthem Insurance Companies
US
For now we are not inclined towards going cloud.
From Pega Multitenancy perspective, can each tenant have their own Pega Data Schema ?
Pegasystems Inc.
US
But you may want to move to the cloud in the future. You want your application ready for that possibility, i.e., be as "cloud native" ready as possible. See https://12factor.net/.
My understanding is that multi-tenancy involves one highly scalable schema where customer data is separated by a tenant or Org id. See: https://www.slideshare.net/developerforce/salesforce-multitenant-architecture-how-we-do-the-magic-we-do
Regarding cloud hosting, see: https://www.pega.com/insights/articles/cloud-multi-tenancy-single-tenancy-does-it-matter
Pegasystems Inc.
US
Pega's multiTenant deployment option is not widely used, but it is a solution for sharing a single application and deployment among several business units / customers where all business units / customers use the same application but have independent and distinctive data and have no access to data outside of their tenant.
In a multiTenant deployment, every table has a pzTenantID column and the pega engine adds "where pzTenantID = " to every query.
Rules and system configuration are stored in the "shared" tenant.
MultiTenancy allows some rules to be customized or delegated by tenant but is really designed for a service provider type application where the tenants just use the application rather than maintain it.
The PDC service is multiTenant.