In the previous chapter, we investigated stability patterns. Stability patterns are here for your application so that it can survive bugs. It is ludicrous to expect applications to be shipped without any bugs, and trying to achieve this will wear your team out. Instead, we learned how to live with it and made sure that our application is resilient enough to live through bugs. In this chapter, we will focus on performance patterns and anti-patterns. These patterns define architectures and practices that significantly affect the performance of your application in a positive or negative way.
In detail, we will learn about the following:
- AJAX overkill
- Unbound result sets
- Proxy
- Filters and Pipes
- Loops
- Change detection
- Immutability
- Prototype and the reusable pool
