Handling Partial Failure - API GW
Handling Failure through API GW:
We have the following ways to handling the Failure(s) .
1) Partial Response to the Consumers :
Consumer invoke the GW's Endpoints which will aggregate more than one endpoints internally , one of the Endpoint will fail due to some reason . In the ideal world client will receive the error in the response . But in GW with MSA world , client will receive the partial response from those active services
2) Response from cache:
Instead of receiving the Error in the response , Client will receive the response from Cache if any service(s) are in inactive mode.
In the API GW world , We can restricted to reach the request to the Service when the services are in inactive mode through Circuit breaker Pattern. It will not allow to reach the client to server if the service(s) are down
Ref
https://www.nginx.com/resources/webinars/mra-ama-part-7-circuit-breaker-pattern/?mkt_tok=eyJpIjoiTlRnd1ptWTJPR0U1TUdKbCIsInQiOiJtTmc5Yzcra3pRSWZqRFVQekpmenFzWEw2blRqeTlGc2t6MUgycHorSzY2RDJkWSs1VUNaenR1cG1UUTdLZnRCQVFqWkFXQWQ0WE1oTFJ4TDJqdXlJbW1jNGVkXC91eFhqRXhWRDdSODVTbDZDbEZSM2ZxMDdhUE05RVAxUXozeXYifQ%3D%3D
We have the following ways to handling the Failure(s) .
1) Partial Response to the Consumers :
Consumer invoke the GW's Endpoints which will aggregate more than one endpoints internally , one of the Endpoint will fail due to some reason . In the ideal world client will receive the error in the response . But in GW with MSA world , client will receive the partial response from those active services
2) Response from cache:
Instead of receiving the Error in the response , Client will receive the response from Cache if any service(s) are in inactive mode.
In the API GW world , We can restricted to reach the request to the Service when the services are in inactive mode through Circuit breaker Pattern. It will not allow to reach the client to server if the service(s) are down
Ref
https://www.nginx.com/resources/webinars/mra-ama-part-7-circuit-breaker-pattern/?mkt_tok=eyJpIjoiTlRnd1ptWTJPR0U1TUdKbCIsInQiOiJtTmc5Yzcra3pRSWZqRFVQekpmenFzWEw2blRqeTlGc2t6MUgycHorSzY2RDJkWSs1VUNaenR1cG1UUTdLZnRCQVFqWkFXQWQ0WE1oTFJ4TDJqdXlJbW1jNGVkXC91eFhqRXhWRDdSODVTbDZDbEZSM2ZxMDdhUE05RVAxUXozeXYifQ%3D%3D
Comments
Post a Comment