| Gliffy | ||||||
|---|---|---|---|---|---|---|
|
Here is a visualization of the SOAJS cloud once deployed.
The entry point to the cloud is Nginx. Remember that Nginx is the web server we configured to forward all incoming traffic to the controller.
Moreover, we have multiple instances of Nginx as well as multiple instances of the controller. This redundancy serves as a load balancer to maintain system-wide high responsiveness and mitigate sluggishness.
After the request is forwarded to the controller, the controller then decapsulates the session to forward the request to the correct service. But this does not happen before some preliminary checks.
These preliminary checks serve two purposes:
- a security feature that stops "bad" requests before the reach the APIs.
- a performance feature that prevents "bad" requests from wasting the services' resources.
After the controller finishes its checks, to delivers the request via round-robin distribution to the next available instance of the required service.
Also note that the services themselves do not interact directly with each other, they always pass through the controller.