Multi-Tenant SaaS Architecture
Yesterday I was talking to one of my friend who is staying in Dublin and In our conversation...he was asking me a question that is not new to me but a FAQ from other friends as well. The 100 Million question is " Even Public clouds has been adopted for 5 to 10+ years now , why I am not working on Cloud".?My Immediate answer was" you are working as an end user on SaaS Tool or a SaaS Product and its Lifecycle Management is taking care by the SaaS Vendor / Service Provider such as Gmail/Workday/ZOHO/ as an Example.? The SaaS model is the most commonly used option for businesses in the cloud market because It’s easily accessible. We only need an internet connection and a browser. In this article I have given a holistic view of the SaaS Cloud Service Adoption and its Solution Architecture Design.
SaaS Hosting Architecture :
In Multi-tenant SaaS hosting option a Single Application Instance shared by all tenants and a mediator determines tenant id in each request so that each application request can be handled properly. Most of the SaaS service providers operate on multi-tenancy because the service provider has to make software updates once due to which its cheaper, faster, efficient resource usage but in case of single-tenant architecture, the service provider must touch multiple instances of the software in order to make updates.
Multi-tenant Microservice SaaS on AWS :
SaaSOps ( SaaS Operation ):
SaaSOps ensures that the right users have access to the right data. It also automates such processes as user onboarding and offboarding. This allows your IT team to focus on more strategic projects. ( image source: bettercloud.com)
Reference: