In the previous chapters, we experimented with API services with the intent of consuming APIs of any type of content that were created by our hypothetical backend. If I had to share a one-liner about what I learned during my online adventures, it would be don't trust anybody...especially not yourself. What I mean by that is that you can never trust an API to work as expected, even if it is your own API. You should always expect everything that can go wrong to, well, go wrong. One of the less harmful things that can happen when trying to communicate with your backend is that it won't respond. While this one-way communication is harmless for your Angular applications, it is most frustrating for your users. In this recipe, we will learn how to implement timeouts in our external call and how to react to unresponsive APIs.
Fortunately, there is a very simple way...