Salesforce architecture best practices. It’s nuanced work that requires experience and lots of clear communication. Platform APIs. The place to get architectural resources that Salesforce stands behind. Wesley Beary. Software engineering can’t be reduced to a set of rules. Choose the right tools for the right task. . There are three essential areas to understand when designing architectures on the Salesforce Platform: Transactions. Transactions. Grasp the foundational layers of Salesforce architecture including cloud services, data security, APIs, and metadata for scalable solutions. Taking on a designer mindset, you can develop “how might we” questions to frame design challenges and inspire alternative solutions, as well as analyze existing processes and workflows to identify bottlenecks and opportunities to improve business outcomes and accelerate delivery. Rather, it’s about understanding the problems we’re trying to solve, and making trade-offs among competing priorities. On the Salesforce Platform, a transaction can be instantiated by code execution and/or a database operation. Choose the right tools for the right task. Sep 14 - 3 min read. Currently there are three decision guides available from Salesforce: Architect’s Guide to Building Forms, Architect’s Guide to Building Record-Triggered Automation and An Architect’s Guide to Migrating 10 Principles for Architecture at Salesforce. Metadata Versus Data. nslwlrlontgajeekyufzcitudrnyiolipcrjhllyzwtfdkcblrpovthhuqz