Salesforce Architect Resources Our Evangelists Recommend

Ask five different architects how they solved a complex problem, and you’ll likely get six different answers. We are a community built on diverse backgrounds—ranging from retired military officers and IT veterans to self-taught developers and admins—and that diversity is our greatest strength. However, even the most seasoned architects don’t work in a vacuum.

In the Salesforce ecosystem, the landscape shifts rapidly. Staying ahead requires more than just experience; it requires a trusted “toolkit” of frameworks, diagrams, and decision guides that provide clarity when the requirements get cloudy.

We often get asked, “What are the resources you actually use when the stakes are high?” To answer that question, we’re pulling back the curtain. From the foundational logic of multi-tenancy to the tactical precision of data model templates, here are the personal favorites that have shaped our careers and continue to live in our “permanent tabs.”

Lilith’s recommendations

Trailhead and I were love at first sight. I had never experienced such an interesting, engaging, hands-on and witty learning platform and I have used it religiously for pretty much all my certifications since. For each certification I completed, the respective Trailhead Academy exam guide was my first go-to, and a Trailhead search for any modules on that product or topic was my second.

The Newest Badges section feels like Christmas morning with tons of new badges, many of which I eagerly favorite or complete. New features like the Activity Streak or community initiatives like 100 days of Trailhead warm my nerdy heart and get me super excited as they allow me to keep on being curious, continue learning, geek out with countless others and finally make some progress on completing my favorite badges. 

Given this, it’s no surprise I leaned heavily on Trailhead during my journey to Certified Technical Architect. Gems like Strategies for Big Data Architecture were instrumental in expanding my knowledge and really helped me better understand big data options and how they compare. 

Nevertheless, at some point in your certification journey, you have to dive deeper: dive into help documentation, data model diagrams, object specifications or architectural fundamentals. The Platform Sharing Architecture Fundamental was the first deep dive I took on my journey to CTA and it remains a constant resource for coaching aspiring architects. Going under the hood to really understand sharing records was such an important step to learning to select the right option for the right situation.

Just like it’s important for an architect to be able to go deep under the hood, into the technical specifics, it’s equally – if not more – important for an architect to train the architect mindset and take on a holistic and strategic perspective. That’s why I was so excited when the Strategic Salesforce Administration Trailhead Module was released. While it’s targeted towards admins, it provides such a good overview of strategic thinking and provides really clear examples and guidance on how to train it.

David’s recommendations

No one is born an architect. I certainly wasn’t. Before working in the Salesforce ecosystem, I served in the Navy as a Naval Flight Officer. My journey into technology began much later when I volunteered to become a Salesforce Admin for a nonprofit. At that point, I was focused on learning the platform and delivering solutions, not thinking about architecture. That perspective started to shift later while working as a partner consultant on a multi-cloud enterprise solution. I began to see that every design decision either creates technical debt or builds a foundation that can scale. The difference often comes down to how deeply you think during discovery and design, before anything is built.

One of the first resources that helped expand my thinking was Trailhead. I’ve always loved its gamified learning approach. A couple of trails in particular helped me move from building features to thinking more strategically about systems. The Learn Strategy Design Trail encourages you to slow down and understand the problem before rushing toward a solution. The Get to Know Relationship Design Trail introduced me to design frameworks such as human-centered design and values-driven design, which reshaped how I approached problem definition and solution design. Together, these resources helped me start looking beyond individual features to the broader design implications of the platform.

As my responsibilities grew, the Salesforce Architecture Center became an essential resource. The Well-Architected Framework and the articles that support it highlight patterns and anti-patterns that influence long-term platform health. Instead of focusing only on solving the problem in front of you, the guidance encourages architects to think about governance, trust, security, and scalability across the entire system.

The final piece of the journey has been the Trailblazer Community. Mentors and peers challenged my thinking and helped me recognize better ways to approach architecture decisions. Just as important is the habit of intentionally seeking mentors from diverse backgrounds and experiences to build a personal “brain trust” that expands how you think about design, tradeoffs, and long-term system impact.

For anyone interested in becoming an architect, start where you are. Practice strategic thinking in your everyday work. Ask questions about design implications and system impact. Have the courage to challenge the status quo when you hear, “it’s always been done this way,” and look for opportunities to improve the design. Over time, those habits build the mindset that defines great architects.

Von Clark’s recommendations

As a programmer and developer who has transformed into an enterprise architect, I’ve built my toolkit around resources that help me dive deep into the technical foundations of Salesforce while staying connected to the community.  The Developer SOAP Guide is my go-to reference when I need to understand the nitty-gritty details of Salesforce objects and API structures. Whether I’m architecting integrations or troubleshooting data model questions, having that comprehensive object reference at my fingertips is invaluable for getting the technical specifics right. I also lean heavily on the Anti-Patterns Explorer as an early warning system, spotting these patterns in designs or code reviews usually signals deeper architectural issues that need attention before they become problems.

Security and sharing are foundational to any solid Salesforce architecture, which is why I keep the Salesforce Sharing and Security Trailmix bookmarked. It’s a curated collection that breaks down complex security concepts into digestible modules, making it perfect for both learning and refreshing my knowledge on org security, record-level access, and sharing rules. When you’re designing solutions that need to balance functionality with proper data governance, this resource is essential.

For staying current with admin-focused announcements, best practices, and product updates, the Salesforce Admins website is my constant companion. It bridges the gap between purely technical documentation and real-world implementation, offering practical guidance that helps me understand how features actually work in production environments. The blog posts and feature spotlights often spark ideas for how to better serve the customers and partners I work with in my evangelism role.

Scott’s recommendations

I joined the Salesforce ecosystem through MuleSoft. I already had a lot of experience in architecture, but the tooling, patterns, and community resources at Salesforce were largely foreign to me. My first go-to for learning was MuleSoft Docs, which was essential for finding information about various connectors that I needed to design and develop on customer engagements. As my career progressed, I noticed there wasn’t a centralized location for delivering MuleSoft projects, which led me to join the team behind Catalyst Knowledge Hub. It became a great resource for customers and partners navigating MuleSoft implementations.

As my scope expanded into the broader Salesforce Platform, Trailhead and Salesforce Developers became my primary sources. Trailhead stands out for its depth as well as breadth in Salesforce technologies and culture, although I tend to favor the hands-on badges. Salesforce Developer fills the complementary role of providing the deep technical specifics that I need when architecting solutions or building proof-of-concepts.  These resources were crucial for understanding the Salesforce AI capabilities that led to Agentforce, and their importance has only grown with continuous innovation.

I’ve also found the Anti-Patterns Explorer from the Salesforce Architecture Center to be a seriously helpful resource. Think of it as a great early warning system for catching when a solution is starting to go sideways. Learning these anti-patterns is a big deal, as seeing them pop up in code reviews or documentation usually points to deeper problems that need attention.

Miriam’s recommendations

When I joined Salesforce eight years ago, I already had a long career in IT and Architecture behind me. To go deep into any ecosystem, I first need to understand the overarching framework. That’s why my first favorite is the Multi-Tenant Architecture documentation. It explains how the platform actually works under the hood which is fundamental to designing solutions that respect governor limits and thrive in a shared resource environment.

As a visual person, the Data Model Gallery is my next essential. Being able to see how various objects relate is invaluable, especially since many are available as editable Lucid templates. I love the level of care put into these often using functional descriptions (like “billed to” or “governed by”) in the relationship lines that clarify exactly how to use those objects appropriately.

In the enterprise world, orgs almost never exist in isolation. Ensuring a design uses the right integration patterns is one of an architect’s most critical tasks. It’s no surprise that Integration was a top-requested topic for Think Like an Architect, which we covered in Episode 2. The Integration Patterns document is one of those resources that is almost permanently open in one of my browser tabs.

Finally, I have a real fondness for the Architect Decision Guides. The latest iterations are masterpieces of clarity, particularly the Record-Triggered Automation Decision Guide. The concept of “automation density” introduced there is an instant classic and it provides a sophisticated vocabulary for a problem every architect eventually faces.

Architects can all agree on something

Architects are famous for being able to argue about almost anything, from naming conventions and data skew to the “perfect” flow vs. code balance. But as you can see from the resources we’ve shared, there is one thing we all align on: good documentation is invaluable.

Whether you are navigating the nuances of multi-tenancy or deciding on your automation density, these guides are the common language that turns a debate into a design. We hope these favorites become as permanent in your browser tabs as they are in ours.