When designing an upstream API and its implementation, the development team has been advised to NOT set timeouts when invoking a downstream API, because that downstream API has no SLA that can be relied upon. This is the only downstream API dependency of that upstream API.
Assume the downstream API runs uninterrupted without crashing.
What is the impact of this advice?
Without setting a timeout for the invocation of the downstream API, the upstream API cannot guarantee timely responses to its clients since it has no control over how long it might take to receive a response. This makes it impossible to provide a reliable SLA for the upstream API as it depends on the downstream API that has no defined SLA. Therefore, the correct answer is that an SLA for the upstream API cannot be provided.
A. An SLA for the upstream API CANNOT be provided.
A. An SLA for the upstream API CANNOT be provided.
Answer: A
Answer: A. A upstream API cannot wait on the downstream API longer than its SLA. If upstream response SLA is 500 ms, then it cannot wait longer than 500 ms for a response from downstream system.