PegaCloud - Hybrid Tenant Model
The following article discusses the shift from single and multi-tenancy models to a hybrid-tenancy approach in cloud services. Hybrid-tenancy, enabled by microservices and containers, combines elements of both single and multi-tenancy to balance performance, security, and cost.
https://www.pega.com/insights/articles/cloud-hybrid-tenancy-replacing-single-and-multi-tenancy
Does anyone know if Pega Cloud has fully adopted this model? Any additional resources to understand this better would be appreciated.
Thanks in advance for your help!
EvonSys LLC.
US
I also would like to know more on this topic, I've not seen any white paper published on this recently.
The insight article talks about how microsvc architecture conforms to multi-tenancy, But how Pega actually achieves this architecturally is unknown. when we say hybrid, primarily there can be two ways I'm thinking, with the new cutomer request the pod structure can be spawned in PaaS , It can connect to the same dB with the 1) conventional tenant id or 1) new schema can be created under same dB server via terraform and deployment pipeline.