Clean Apex Code: Software Design for Salesforce Developers

© The Author(s), under exclusive license to APress Media, LLC, part of Springer Nature 2025

P. GonzalezClean Apex Codehttps://doi.org/10.1007/979-8-8688-1411-2_7

7. Cascading Failures in Trigger Boundaries

Pablo Gonzalez¹  

(1)

Dublin, Ireland

 

At the end of the day, it's important that your requirements drive the architecture rather than the other way around.

—Dan Appleman

In the previous chapter, we discussed several techniques for validating parameters and variables. The whole reason for doing these type of validations is to prevent errors or exceptions in our code. However, there are some types of errors and exceptions that are much harder to reason about, especially because they require a deep understanding of Apex’s transaction model. In this chapter, ...