Summary

In this chapter, we have covered a number of the different architectural decisions that will impact the performance of your application, both in terms of resource usage and developer productivity. We started by discussing the impacts of using licks or code in our application and how to determine the best solution at the time. Following this, we moved on to discuss code structure and linting to help ensure that common bugs or performance issues were caught early.

This led into a more general discussion of the use of object-oriented patterns in Apex and how they can help make it easier to test and profile our code for scale, as well as ensure that we can modularize our code for increased developer performance as we make changes in the future. From here we dove into specific architectural trade-offs that you need to consider when designing different types of solutions using Apex.

Finally, we finished the chapter with a discussion on managing the performance of an application...