In this section, we'll improve the behavior of our application while using functionalities provided by third parties (like the one used so far, Twitter). Such services aren't always very efficient or may encounter some problems or maintenance.
The problem with that is its independence from our code, we don't have any control. While they help us for some parts of our application, these third parties can also break our performance. This impact comes from the fact that we're using them in actions that have to wait for an external request to respond or to fail with a timeout.
In such cases, our server can become stuck really quickly by waiting on a large number of third-party requests to release. But thinking further, we should be wondering why those actions are blocking our threads and preventing other requests being handled by the server? This makes no sense; the action, which is under the covers waiting for a remote procedure to end, should release the thread and wake...