-
Notifications
You must be signed in to change notification settings - Fork 8
Use case : load balancing
Marwane Kalam-Alami edited this page Jun 20, 2012
·
5 revisions
<<< Back to [[Final soa model design]]
A company exposes an Endpoint for a web service, which is meant to be consumed by several Organizations. This endpoint is only a front-end that acts as a load balancer for multiple Endpoints that expose the same underlying web service.
Goals:
- Make EasySOA check the URLs configuration for the front-end, to ensure that all URLs lead to the same webservice, only on different endpoints?
- Be able to list all endpoints hidden behind the load-balancer, and make sure that they match the same service
- Monitor these endpoints to check their availabilty and the front-end respect of the SLR
- 1 Service "MyService"
- 1 Deployable "MyServiceCode"
- n DeployedDeployables on Production, that:
- Exposes 1 "MyServiceCode" endpoint per deployed deliverable (total: n Endpoints)
- n DeployedDeployables on Production, that:
- 1 Deployable "LoadBalancer"
- 1 DeployedDeployable on Production, that:
- Exposes 1 "LoadBalancer" endpoint
- Depends on n "MyServiceCode" endpoints
- (EITHER not EasySOA-managed) Has the mappings specified by import/by hand on the DeployedDeliverable
- (OR, EasySOA Integration) Has the mappings specified by import/by hand on the DeployedDeliverable, with the mappings being used to configure the load-balancer
- 1 tailor-made ModelConstraint to make sure all endpoints we depend on are of the same implementation "MyServiceCode" of the Service
- 1 (scheduled) SLR Validator to check for the quality of the service
- 1 DeployedDeployable on Production, that:
- 1 Deployable "MyServiceCode"