...
| View file | ||
|---|---|---|
|
This is the current view of how the service will work, with the back end making calls out to TIS Core to pull in data not duplicated in Revalidation.
The disadvantage with this approach is the tight coupling between the back end and TIS Core which means routing complexity, monitoring and recovery is added to the back end. Managing messages to other services should not be the responsibility of the back end.
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.
Alternative design featuring a bespoke controller
...
| View file | ||
|---|---|---|
|
Adding a bespoke controller to the design will allow the orchestration between different services to be abstracted from the back end. The controller would be responsible for splitting requests between the data providers and aggregating the responses before the reply goes back to the client
Alternative design featuring a message broker
...
| View file | ||
|---|---|---|
|
Rather than write a bespoke controller