Current architecture design as discussed starting 16/04/2020
...
| View file | ||
|---|---|---|
|
...
The complexity of the back end will be increased each time it needs to talk to another service, e.g. Self Service for Form Rs or future GMC Connect APIs.
Long term design featuring a message broker
...
| View file | ||
|---|---|---|
|
...
With our current, envisaged configuration there would be very little custom code required to be written for the integration service. Most of our requirements would be handled by configurable settings in Camel.
Single request/response timeline
...
| View file | ||
|---|---|---|
|
...
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.
Current Implementation
This is the current implementation in stage-revalidation as at Fri 24/04/2020:
...
| View file | ||
|---|---|---|
|
Detailed AWS Architecture
This is the architecture for the Revalidation service as at Friday, 18/05/2020
...