...
This solution is the most flexible when it comes to adding extra services that need to be consumed.
Single request/response timeline
...
| View file | ||
|---|---|---|
|
This diagram shows the path a request takes through the components of the service in the case of a request for dynamic data from the back end. The diagram illustrates the use of a controller, but the concept is the same where no controller or a broker is used.
The steps are
The client makes a request from the internet
Route 53, or other DNS directs the request to the Revalidation service
The WAF checks the incoming request is acceptable
API Gateway routes the message to the controller
The controller routes messages to the back end and TIS Core via private API Gateway calls
The back end and TIS Core send their responses back to the controller via the gateway
The controller aggregates the response and returns it to the public API Gateway
The public API Gateway sends the response back to the client via the WAF and Route 53.