Introduction

This tutorial consists of five steps.

By following the procedures from Step 1 to Step 5, the basic chat system will undergo a transformation into a Software as a Service (SaaS) model, supporting multi-tenancy and enabling control through pricing plans. The specific details applied at each step will be incorporated into the application in the order depicted in the following diagram.

This process will result in the development of an enhanced chat system, capable of accommodating diverse user needs through the support of multi-tenancy and flexible control via pricing plans.

Check the diagram to see the difference between the architecture before and after the tutorial.

Before the tutorial

After the tutorial

Migration of User and Tenant Information:
SaaSus Platform manages user information and the tenant information associated with it. Therefore, there is no need for the chat system to maintain this information.

External Delegation of User Authentication:
User authentication is delegated to SaaSus Platform. The chat system only needs to receive callbacks from SaaSus Platform and perform necessary processing to implement the login functionality.

Changes to Data Model:
A tenant_id column will be added to the data model previously maintained by the chat system. This enables multi-tenancy support.

By following these steps, the chat system can be SaaS-enabled using SaaSus Platform.