Salesforce Architects’ Post

"The roles of builder and architect are not mutually exclusive. The growth of the Salesforce ecosystem has created many builder-architects. Maybe the funnier definition is true: “Those who can’t build, architect.” My favorite analogy as a project architect is taking on the role of a certain web-slinging superhero. Seeing things that need to be connected and locking them together by creating a bridge of understanding. Sharing the relationships between indirectly connected concepts. Shooting webs of understanding to connect people and ideas. Just your friendly neighborhood pattern-human" from "Practical Salesforce Architecture" https://lnkd.in/g7btvhmS 😀

Building a client's Salesforce #architecture is a wonderful job that has its fair share of responsabilities. There's not an one size fits all approach to designing solutions. If you don't understand what's needed and make concessions, you may have issues in the future. Here are some tips to have in mind when designing a solution. Would you add something to it? Comment-I'd love to know about it! And if you want to know more about the Salesforce and #consultancy ecosystems, be sure to follow me.

Unlock the power of the Salesforce Architecture Dual Funnel Map! Forget the old single funnel model - Salesforce was initially built around it, but let's face it, buyers and businesses operate differently now. Dive into its dynamic features, revamp your sales strategy, and download now! https://lnkd.in/eD7RsyUv #abm #accountbasedmarketing #b2bgrowth #b2bleadgeneration #foundandchosen #salesstrategy #salesgrowth #salesforce #salesforce

In at least 80% of all cases the architectural design of your services should 100% follow the defaults of your Internal Developer Platform. Let me explain: It's a miss-conception that if it comes to architecture of software the platform should follow the service design. If you need "n" de-facto mini-platforms for "n" of your special snow-flake services - you end up with "n" things you need to maintain. The relativ gain in efficiency of the resource or service is in no relationship to the added overhead. Engineering teams today have long factored the cost of this approach into their head-count - which doesn't make it less absurd. I'm aware you will hate this comparison but I'll still make it: no sane sales operations team in the world (at least no good one) would even think about building a CMS that fits their exact process. They've long realized that no matter how many design flaws Salesforce has you should (wherever possible) structure your process following Salesforce-architecture. There is zero reason to believe things look different in software world. The less pipelines, database configs, cluster setups and networking rules the more productive your setup. In 80% of cases you should be totally fine with 3 configs for DBs of type Postgres in staging, you don't need more. The remaining 20% shouldn't be on a platform. Engineering team design is structured to please every single individualist on the team. And because the buying power of those individualists is in no relation, managers do not effectively implement standards. What the ICs don't get: they are paying the price for the perceived freedom. The price are long waiting times, sign-off cadences, tickets and frustrating standards. I've recently seen a statistic of a team estimating an average of 13 weeks to setup a new service incl. all environments. Using highly standardized IDPs you can do this in 5 minutes at max. Standardization means freedom. IDPs are what everything will convert to and those who get it first make the strongest leap forward. You can wait, but it will come.

TrailblazerDX was a crucial event for Salesforce Architects looking to stay at the forefront of technological advancements – with a goldmine of insights, strategies, and trends. Andrew breaks down the key takeaways for architects. https://bit.ly/3VcnSDM #Salesforce #TDX24

I often hear people talking about Salesforce Flow, discussing what it can achieve, but I rarely see anyone emphasizing design principles or design patterns in its use. This is the fundamental crux of the issue. Anyone can build a flow, but the crucial question is whether it will genuinely contribute to business value without considering a futuristic vision and the right design principles. Unfortunately, I believe it won't. Yes, anyone can create a flow, but there's a significant difference between constructing one with the right architecture and merely addressing the current problem at hand. If a flow is built without considering the broader architectural perspective, it may not qualify as a great architecture, and it might not bring sustained business value in the long term. As long as I don't see that conversation I am afraid I do not see that as an architecture conversation I rather take it as a tool conversation . If you are a salesforce architect I would love to see you take the following aspects into consideration Modularity, Scalability, Reuse and Composition, Error Handling, Governance and Security, Documentation, Testing, User Experience, Integration Considerations, and Performance Optimization.

Architect Fundamentals 2: System Architecture Good morning, LinkedIn community! 🌟 Welcome to Day 2 of our Salesforce Architect Fundamentals series. Today, let’s tackle Salesforce System Architecture. 🏗️ While it sounds technical, system architecture should always reflect the user story. For example, Salesforce is at the center where sales agents help customers find products, and the payment gateway on the right facilitates credit card payments, linked to our webshop. Don't be daunted; "System Architecture" simply answers: What systems do we have, why are they connected, and what does each do? You only need a few boxes on a PowerPoint slide and some lines connecting them. Keep it simple; often, a basic setup is more effective than complex ones. 🚀 Just get started! And you know what? Why don't you draw a system architecture of your current project or org right away? Take yourself 30 minutes, that's all, and see how far you get. And let me know how it goes! #Salesforce #SystemArchitecture #SimplifyTech #ProjectManagement

I've just posted my review of "Practical Salesforce Architecture" by Paul McCollum, UXMC - you can find the full video here on YouTube https://lnkd.in/eB6dJNZM Paul has written a great book 📖 full of useful advice that I would recommend to any enterprise architects trying to understand #Salesforce or #salesforcearchitect wanting to understand enterprise architecture a bit better. It's also a fantastic book for anyone working with Salesforce who wants to: 💬 communicate how Salesforce works to non-Salesforce people more effectively 📄 understand some documentation best practices and principles 🤝 understand what can be expected of different architect roles and how to succeed as an architect

https://lnkd.in/ecYEQ6VN For architects, consultants and admins who are looking to create diagrams to showcase there solutions, here is a refresher article on salesforce diagrams which you should leverage. It has templates for quick reuse and get the right diagram for your needs.

We're excited to present Maciek Simm, who will be leading an enlightening session titled "Keine Grenzen? About the importance of boundaries." Ever felt like Indiana Jones running from a giant ball when navigating through complex Salesforce environments? Maciej knows the feeling all too well. He's here to guide us away from the chaos of the "Big Ball of Mud" - a term for systems that are disorganized and tangled messes of code. In this session, Maciej will delve into: * The critical need for clear boundaries in software architecture Strategies to avoid creating a "Big Ball of Mud" * Insights into Domain-Driven Design (DDD) and its importance * Practical patterns for solving common architectural challenges Prepare to transform your approach to Salesforce environments with Maciej's expert strategies for maintaining clarity and structure. 🛠️ 🌟 Don't miss this opportunity to redefine the boundaries of your Salesforce projects. Secure your spot at Polish Dreamin'24 now and join us for a journey towards cleaner, more efficient Salesforce environments. Buy your tickets today! www.coffeeforce.pl/dreamin #PolishDreamin24 #polishdreamin #coffeeforce #Salesforce #SoftwareArchitecture #DomainDrivenDesign #TechConference