Summary

In this chapter, we have covered asynchronous code, when it is used, and for what purposes. It is clear that asynchronous code becomes harder and harder to read and maintain as it grows, giving rise to patterns such as callback hell. There are several techniques to deal with this, as described throughout this chapter. Changing your coding style a little is one way. Looking at constructs such as promises, especially in conjunction with async/await, is another way. Using async/await means we suddenly get something that can be likened to order in your async code. We have tried to keep things as framework free as possible as it is important to understand all the mentioned concepts without mixing them up with concepts from a specific application framework. One thing can be said though: Angular allows you to use whichever asynchronous method you want to organize your code. Doing...