Several problems to be considered and solved in the design of multi tenant architecture

Thinking about distributed multi tenant architecture

Now we are developing software in the market SAAS Standardization is already standard , Combine current or distributed microservices with SAAS The actual situation and needs of multi tenant structure , As a technical architecture, how can we consider designing a flexible architecture scheme for multi tenant dynamic data source switching under distributed microservices , It is an important thing at present . The following analysis is made for multi tenant dynamic data sources .

Scene analysis

Scene one :
The front end directly initiates a request to the back-end service through the gateway , If there is only one service , The data source needed to handle the current execution of the accessed service should be the data source of the tenant of the current login user
The sequence diagram is as follows :

Scene two :
Multiple services cooperate to complete a business , Directly above

Scene three :
Multiple services cooperate to complete a business , And some business functions are processed asynchronously , Pictured

Scene 4
The processing scenario of distributed scheduled tasks in the multi tenant scenario

Refer to the post
Put your web Turn the application into a multi tenant SaaS Solution
https://www.ibm.com/developerworks/cn/cloud/library/cl-multitenantsaas/
be based on spring Realize multi tenant applications through multiple data sources
https://www.jianshu.com/p/54f35fa2f374
be based on Hibernate Dynamic data source switching :https://blog.csdn.net/sysushui/article/details/90319375
example ：https://blog.csdn.net/lulitianyu/article/details/79566775