Tenant Load Balancing Explanation in Level 4 SaaS Maturity Model

I have already done some research on SaaS maturity based on the Gianpaolo SaaS maturity model .

I am currently confused about the maturity level of SaaS 4. He said that he has a “load balancer” that dynamically invokes a new instance of the load balancing application for the SaaS application.

I want to know what this "tenant load balancer" really means. How do we implement this “tenant load balancer" in the real world or on the application server?

Can someone give me a good explanation and example, for example, implementation in Java EE technology?

+3
source share
2 answers

The key concept is horizontal scalability with load balancing. At a high level, this is similar to the ESB / load balancer used in the SOA environment.

The following are some of the features of a load balanced SAAS deployment:

1) More than one instance of SAAS software has been completed.

2) The tenant’s call for software can be processed by any of the instances. A load balancer takes care of routing tenant requests to one of the instances based on load balancing strategies.

3) . , , . , EC2, SAAS . . EC2.

​​ ESB / / .

-, , , .. SAAS, .

+2

:

  • - , A, B, C. .
  • - - , ..
  • - . .. -.
  • , (A, B C).
  • , .

, :

  • www.example.com
  • a.example.com, b.example.com, c.example.com
  • , www.example.com.
  • , www.example.com
  • a.example.com .

Salesforce.com. .

+3

All Articles