<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by José Garcia Ponce on Medium]]></title>
        <description><![CDATA[Stories by José Garcia Ponce on Medium]]></description>
        <link>https://medium.com/@josgarca?source=rss-52f0339b1218------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*R32O7OLnzIh1nNCjTWl80A.jpeg</url>
            <title>Stories by José Garcia Ponce on Medium</title>
            <link>https://medium.com/@josgarca?source=rss-52f0339b1218------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 04:11:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@josgarca/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Let’s talk about tea]]></title>
            <link>https://medium.com/@josgarca/lets-talk-about-tea-22f67753e604?source=rss-52f0339b1218------2</link>
            <guid isPermaLink="false">https://medium.com/p/22f67753e604</guid>
            <category><![CDATA[fish]]></category>
            <category><![CDATA[blackwater]]></category>
            <category><![CDATA[fishkeeping]]></category>
            <category><![CDATA[fish-tank]]></category>
            <category><![CDATA[aquarium]]></category>
            <dc:creator><![CDATA[José Garcia Ponce]]></dc:creator>
            <pubDate>Fri, 19 Sep 2025 23:04:13 GMT</pubDate>
            <atom:updated>2025-09-19T23:04:13.255Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/392/1*jqx1pntTaisJK-Ebv__4SQ.jpeg" /></figure><p>Part 2 – An amazonian tea tank</p><p>While I explained in the previous article why I wanted to have an Amazonian aquarium that represented a little piece of Peru, I did not explain why I got hooked to the idea of attempting to build specifically a <strong>blackwater</strong> type aquarium.</p><p><strong>So what is a blackwater aquarium and what is so cool about it?</strong></p><p>In the Amazon basin there are several river types, but to keep things simple we can reduce them to three: clear, white, and blackwater.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*S0Ti4RTrLIJIuR9WxSs5qA.jpeg" /><figcaption>clearwater, whitewater and blackwater rivers</figcaption></figure><p>When we think about tropical fish aquariums we usually picture the clearwater tanks we see in stores or in people’s homes. These aquariums tend to have a mix of freshwater fish from all over the world that can co-exist because of size and because <strong>they can tolerate</strong> the range of water parameters these tanks tend to have, which are typically quite neutral in terms of pH and hardness.</p><p>While there is nothing wrong with having a variety of fish from different environments into the same water type this <em>per se,</em> the focus with this approach is essentially on keeping the fish alive within an acceptable range and even a stronger focus on aesthetics. The focus is not so much on giving the fish the best possible conditions they need to truly thrive.</p><p>Keeping in mind I wanted a true ecosystem. I researched for types of ecosystems around <strong>Iquitos </strong>and<strong> </strong>I came across the concept of Blackwater rivers. As the name suggests, these rivers consist of very dark or <strong>stained-like tea water</strong>. Whitewater rivers tumble down the Andes, carrying sediments and minerals. <strong><em>Blackwater</em></strong> rivers are different: they flow through dense rainforest across sandy, nutrient-poor soils. Because the water is low in minerals, it stays very soft. Submerged roots, fallen branches, and leaves then release tannins that darken it, giving it that mysterious tea-stained look.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vQ_hhFSuhkOpKRvAc3S_Fw.png" /><figcaption>The “Meeting of Waters” in Brazil. The Rio Negro (blackwater) meeting the Amazon river (whitewater). They go on for kilometers without fully mixing due the difference in parameters in the water. I am hoping one day I can visit this place.</figcaption></figure><p>The water in this ecosystem is special enough that only certain species can thrive here. My perspective is that many fish species we find in stores like some Tetras, Angelfish and dwarf cichlids learn to survive in standard fish tanks but they should thrive when brought into a blackwater tank as this would resemble the environment in which they evolved.</p><p>Once I understood what blackwater meant in the wild, I knew I wanted to bring a little piece of it into my living room so that those fish would feel at home…. remember? Like how I wanted to feel… <strong>But how do you turn Irish tap water into Amazonian tea? </strong>You won’t find the answer in a box of Barry’s. That is where the fun and the challenge begin.</p><h3>Setting up the tank</h3><p>And so, once the decision was taken I reached out to a neighbour who has an aquarium accessories business. A couple of days later he delivered a 240 litre tank with a cabinet I had to assemble, along with an external filter, heater and lights. Most of these came from Poland. In retrospect, I made the same mistake I did when I dug the garden pond: I should have gone bigger from the start 😌 . But this is one of those decisions that is not easy to reverse, and you usually realize it once you are already too deep into it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IsyFRiPoRvTBA9HBNK8mZA.png" /><figcaption>The corner of the living room Ariana generously sacrificed.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J9wkjnoB6Wi_nUEN11e00w.png" /><figcaption>240 litres of potential</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fr9JaFU5SwccS1eiMqnT0Q.png" /><figcaption>Building the cabinet itself was not hard, but I took my time. Fingers crossed it holds 300 kg of water 😬</figcaption></figure><h3><strong>From Theory to Praxis</strong></h3><p>If you read the previous article, you may remember how I ambitiously talked about building a true <strong>Nanay River</strong> biotope. It did not take long after setting up the tank for reality to hit me: I had been a bit naive to think I could fully recreate such a complex ecosystem, this is nearly impossible from thousands of kilometers away, in a completely different environment. What I was really building was more of a style, or a <em>biotype</em> in spirit, rather than a precise biotope.</p><p>Still, I wanted to keep it as “Peruvian blackwater” as possible, so I did my research.</p><p>The <strong>foundation</strong> had to be river sand, close enough to what I’d seen in footage from the Nanay. It seemed like an acceptable and accurate choice. I wasn’t overly concerned with the colour as I knew the aquarium floor was eventually going to be a layer of decaying leaves and tree pods.</p><p>I went easy on stones, I read that these rivers do not have as much stones as a whitewater river. I also took into consideration that my choice for stones could adversely affect the water hardness and pH I was trying to reach by introducing too many minerals. A simple test was to add a few drops of vinegar on top of the stone, if it didn’t have a fizzy reaction, it was safe to introduce.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7ZpTlXedmsBOuG0Wbub_Rw.png" /></figure><p>With the sand and stones sorted, the next step was to bring the riverbed to life with leaves, pods, and branches.</p><p>I have to admit I felt a bit silly buying dry leaves online when you could argue they might just as easily be picked up in a local forest. The reality is that I was too excited to make progress and patience has never been my strong suit; and in my defense, they were quite cheap.</p><p>The two main leaf choices I found online were Indian almond and oak. Both are not only attractive in the tank but also help reduce the pH slightly while giving the water its characteristic tea-stained look. As the weeks go by, the decomposing leaves also create a microfauna that benefits the fish and the ecosystem as a whole. I added some <strong><em>Jequitibá</em> seed pods, alder cones, and casuarina pods </strong>as well. In the blackwater aquarium world, all of these leaves and pods are grouped under the name <em>botanicals</em>. Following online advice, I boiled my botanicals for about ten minutes before adding them to the tank to avoid introducing unwanted bacteria. One disadvantage of collecting these materials from the wild is that you never know if they have been exposed to pesticides, which could be fatal for our little gilled friends.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fJSMOg2LVaWyA7Wbsbokwg.png" /><figcaption>Boiled Casuarina pods</figcaption></figure><p>Finally, I prepared the azalea roots by putting them in boiled water and soaking them for a day. Putting them later in a tank was a bit of a challenge as they had not been been soaked properly so I had to temporarily tie them to stone to prevent them from floating.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NJ7bj-yk3crajLzoYgPApw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*elOGdGrG6GJnifjaizusPg.png" /></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F1120309221%3Fapp_id%3D122963&amp;dntp=1&amp;display_name=Vimeo&amp;url=https%3A%2F%2Fvimeo.com%2F1120309221&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F2061022039-4b5bdd32e6045eb985253ce85db2cef2465ef46771b08b69f31d3fac308547b9-d_1280%3Fregion%3Dus&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/ad47163658fbf416658c5e8613d941fb/href">https://medium.com/media/ad47163658fbf416658c5e8613d941fb/href</a></iframe><p>So that was the tank after its first few days: not yet a real home for fish, still finding its balance. The real transformation was yet to come. In the next part, I’ll show you how the water darkened, how the botanicals settled, and most importantly, how the first fish and plants finally moved in.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=22f67753e604" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A blackwater river, a fish tank, and a journey back to our roots]]></title>
            <link>https://medium.com/@josgarca/a-blackwater-river-a-fish-tank-and-a-journey-back-to-our-roots-aed16ff76147?source=rss-52f0339b1218------2</link>
            <guid isPermaLink="false">https://medium.com/p/aed16ff76147</guid>
            <category><![CDATA[family]]></category>
            <category><![CDATA[freshwater]]></category>
            <category><![CDATA[fish]]></category>
            <category><![CDATA[fish-tank]]></category>
            <category><![CDATA[blackwater]]></category>
            <dc:creator><![CDATA[José Garcia Ponce]]></dc:creator>
            <pubDate>Thu, 11 Sep 2025 17:51:58 GMT</pubDate>
            <atom:updated>2025-09-11T21:59:24.003Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Part 1 — Take me home</strong></p><p>When we moved into our current house back in 2023, I knew I wanted our living room to feel like home. By that I mean the decorations, the colors, and if possible even the smells of what we, a couple that is half Guatemalan and half Nicaraguan, and a Venezuelan with Peruvian roots, would call home. I imagined Mayan and Aztec masks, Inca paintings, and so on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vPOo-Tyz8JR2UPEOlzjb_A.png" /><figcaption>A few of the decorations we have been adding</figcaption></figure><p>Little by little we have started to add a mask here, a tapestry there. It is starting to look good, but we still have a lot of traveling to do before it becomes as diverse as we would like. (Admittedly, right now it looks mostly Guatemalan.)</p><p>There was a corner in the living room that had become the temporary spot for my daughter’s play kitchen. Honestly, it was turning into an eyesore (I am sorry Ariana, one day you will understand). I started thinking about what could go there instead, and it didn’t take long before I imagined the perfect thing: a fish tank. I haven’t had one for years, and it felt like the right time. But I also wanted it to carry the same symbolism as the rest of the room, it had to represent something from the Americas. The obvious answer? A true Amazonian fish tank.</p><p>Before I dive into the actual tank, I should say that aquariums were an intrinsic part of my childhood. I literally grew up among fish. They were almost like my little siblings, constantly changing, coming and going. My dad’s obsession with tropical fish meant we had tanks in almost every room of the house. I ate refried beans most nights watching corydoras sift through the sand in the dining room. I watched movies with South American cichlids fighting for territory beside us in the living room. I fell asleep to the hum of the filter in the bedroom tank that held guppies, mollies, and swordtails. At one point, I counted more than 50 tanks in the house.</p><p>My dad has loved fish ever since he was given a goldfish at age 10. Later, financial pressures pushed him toward accounting instead of biology or veterinary school, but his passion never went away. To me, he was and is like the Rick (from <em>Rick and Morty</em>) of tropical fish: always experimenting, connecting tanks with messy tubes, breeding Artemia, and speaking with contagious excitement about some new discovery.</p><p>Back to the project. I must be going through some sort of existential crisis, because I not only became attached to the fish tank idea which was taking me back to my childhood but I also became obsessed with the idea that it had to be as genuinely Amazonian as possible. After hours of ChatGPT research (yes, I went deep), and evaluating the types of Amazonian biotopes I could try to create, I decided the tank should represent a very specific ecosystem: the Nanay River. The Nanay is a tributary of the Amazon in northeastern Peru, and not just any tributary, it’s the main source of drinking water for the city of Iquitos, where Carla’s father is from. And a place that I have been dreaming of visiting for years.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZAvjFk_mzkQxb2cvugiZWw.png" /><figcaption><strong>The Nanay River begins in the protected forests of the Allpahuayo-Mishana National Reserve in northeastern Peru.</strong> Flowing through pristine rainforest, it travels more than 300 kilometers before joining the mighty Amazon River at Iquitos, the largest city in the Peruvian Amazon.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9WhEIn1ANBY_AvvUxgS96w.jpeg" /><figcaption>In its journey, the Nanay provides fresh water, supports local communities, and sustains a rich variety of wildlife.</figcaption></figure><p>Choosing this river meant one thing: I had to understand what makes its ecosystem unique. The fish species, the plants, the pH, the temperature, the geology. One thing became clear very early on: this was going to be a blackwater tank, something I had never tried before or had seen my dad do.</p><p>To be continued…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aed16ff76147" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Reusability Fallacy]]></title>
            <link>https://medium.com/@josgarca/the-reusability-fallacy-0acc4c22c93a?source=rss-52f0339b1218------2</link>
            <guid isPermaLink="false">https://medium.com/p/0acc4c22c93a</guid>
            <category><![CDATA[salesforce-architect]]></category>
            <category><![CDATA[software-quality-model]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[reusability]]></category>
            <category><![CDATA[software-architecture]]></category>
            <dc:creator><![CDATA[José Garcia Ponce]]></dc:creator>
            <pubDate>Fri, 20 Dec 2024 12:26:15 GMT</pubDate>
            <atom:updated>2024-12-21T11:00:04.737Z</atom:updated>
            <content:encoded><![CDATA[<p>Architects, developers, and engineering managers often hear the advice: “Make sure the component is reusable!” It sounds like unquestionable good wisdom, as listening to someone advising you to sleep well and drink enough water, and it appeals to our desire for efficiency, elegance, and long-term planning. It sounds like what every architect should be doing all the time. However, this idea, when followed without question, can lead to wasted effort, bloated designs, and components that are either never reused or don’t fit their intended purpose. Let’s consider why “always building reusable components” can be misleading and how we can think more critically about reusability.</p><h4>The Universal Key</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/909/0*qmCg5c2N3UuMUhoD.jpg" /></figure><p>Imagine a locksmith tasked with creating a key that could unlock any door or as many doors as possible. The locksmith, in their ambition, comes up with a complex mechanism with countless notches and moving parts. After months of effort, the key is completed, but there’s a problem: it’s unwieldy, difficult to manufacture, and only works on a handful of doors. Meanwhile, other locksmiths using simple, tailored keys have already unlocked most doors efficiently and moved on.</p><p>This is what happens when developers aim to create components that attempt to “fit” any future use case. The ambition for universality often leads to components that are overly complex, underperforming, and, ironically, seldom reused.</p><h3>Why “Reusable Components” Often Fail</h3><ol><li><strong>Lack of Context</strong>: Reusability requires abstraction, and abstraction requires deep understanding of the varying contexts in which the component will be used. However, most teams lack the time to explore and understand in detail every potential use case. As a result, the component’s design either misses key requirements or becomes so generalized that it is impractical.</li><li><strong>Overengineering</strong>: Building for reusability involves significant upfront design effort. Developers need to consider edge cases, extensibility, configurability, and compatibility. This investment is rarely justified unless the component’s reusability is both frequent and impactful.</li><li><strong>False Reusability</strong>: Components often end up being “reused” only within a narrow scope, such as within the same application or by a single team. This limited reusability doesn’t justify the complexity and additional time introduced during their design and development.</li><li><strong>Maintenance Overhead</strong>: The more “universal” or reusable a component aims to be, the harder it becomes to maintain. Minor changes to accommodate one use case can inadvertently disrupt others. What starts as a reusable asset may evolve into a liability.</li></ol><h3>The True Cost of Abstraction</h3><p>True reusability demands abstraction, and this requires a process of identifying the commonalities across diverse use cases and encapsulating them into the design. However, abstraction can be expensive. It requires:</p><ul><li><strong>Domain Expertise</strong>: Deep knowledge of the problem domain and future requirements.</li><li><strong>Iterative Refinement</strong>: Reusability is often a result of iterative design, not something achieved on the first attempt.</li><li><strong>Collaboration</strong>: Input from multiple teams or stakeholders to ensure the abstraction aligns with broader needs.</li></ul><p>Many teams underestimate these costs. They assume that reusability is a shortcut to efficiency, when in reality, it often delays delivery and increases complexity.</p><p>Gregor Hohpe has a <a href="https://www.youtube.com/watch?v=aWZFRk-w3ng">great talk</a> on good abstractions as a topic alone if you are curious to dive deeper into this.</p><h3>So…When Should You Pursue Reusability?</h3><p>Reusability isn’t inherently bad. In fact, it’s a cornerstone of good software design when applied using critical thinking. Here are guidelines for when to pursue it:</p><ol><li><strong>Proven Need</strong>: Prioritize reusability for components that have demonstrated potential for repeated use across projects or teams.</li><li><strong>Shared Standards</strong>: Components like authentication modules, logging frameworks, or UI libraries often benefit from reuse because they align with organizational standards.</li><li><strong>Constrained Scope</strong>: Keep the scope of reusability narrow. Instead of trying to build a component that fits every scenario, focus on specific, well-defined use cases. You should rather deliver a solid reusable component within a limit scope than a flaky or hard to use component that attempts to cover a large variety of scenarios.</li><li><strong>Incremental Approach</strong>: Start with a simple implementation tailored to immediate needs. Refactor and generalize over time as reuse opportunities arise. This implies, you must have the time available and estimated in the project to account for multiple iterations. If the project is on tight deadline or budget, a good reusable component is unlikely to be a good idea.</li></ol><p>Instead of defaulting to “always building reusable components,” follow a pragmatic approach:</p><ol><li><strong>Focus on Problem Solving</strong>: Prioritize solving the immediate problem well over building for hypothetical future scenarios. Experience has taught me that obsession with potential but unclear future problems and use cases often leads to analysis paralysis and wasted efforts.</li><li><strong>Adopt Modular Design</strong>: Build small, focused components that are easy to understand and compose. Modularity often naturally lends itself to reusability without overengineering. Domain-driven design can be an effective approach to this as it will help provide a clearer view on the core components where most the effort should go and the ones that could benefit from more simple or generic solutions.</li><li><strong>Embrace YAGNI</strong>: “You Aren’t Gonna Need It” is a valuable principle. Build only what is necessary today, and leave room for adaptation tomorrow.</li></ol><h4>TLDR;</h4><p>Reusability is a powerful tool when used wisely, but it’s not the magic answer to every problem. The effort to make something reusable can sometimes outweigh the actual benefits. The key is to understand when reusability makes sense and when it doesn’t. By keeping our designs focused on solving immediate needs and remaining mindful of where reuse and future-thinking truly adds value, we can avoid overengineering while leaving space for flexibility. The best solutions don’t just promise elegance, they deliver it, without unnecessary complications. <strong>Good architecture is not the one that accomodates for every possible future need but the one that can Adapt easily when the situation demands.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0acc4c22c93a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building Well-Architected Salesforce Solutions Using Domain-Driven Design]]></title>
            <link>https://medium.com/@josgarca/building-well-architected-solutions-using-domain-driven-design-3bddc84fb09b?source=rss-52f0339b1218------2</link>
            <guid isPermaLink="false">https://medium.com/p/3bddc84fb09b</guid>
            <category><![CDATA[salesforce-architecture]]></category>
            <category><![CDATA[decomposition]]></category>
            <category><![CDATA[domain-driven-design]]></category>
            <category><![CDATA[ddd]]></category>
            <dc:creator><![CDATA[José Garcia Ponce]]></dc:creator>
            <pubDate>Wed, 01 May 2024 10:23:12 GMT</pubDate>
            <atom:updated>2024-05-13T10:26:10.124Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9bGkbtOmKCqvp7ccqmcl4g.png" /></figure><p><em>In a dimly lit, ancient cave, a group of prisoners has spent their entire lives chained. All they see are the shadows cast on the wall by figures passing in front of the cave. These shadows form their entire perception of the reality outside. However, one prisoner is freed and steps outside the cave into the sunlight for the first time. The brightness is overwhelming, and he initially squints and struggles. But as his eyes adjust, he sees a world of vibrant colours, diverse landscapes, and the true forms of the figures whose mere shadows he used to watch. He realizes the depth and richness of the world beyond the cave, far different to the limited and distorted shadows on the walls inside the cave.</em></p><p>In this philosophical allegory (“Plato’s Cave”), Plato was referring to how acquiring knowledge and questioning our understanding of the world can change our perception of reality, and the more you know, the more your perception of reality changes, he also proposes that you can use that knowledge acquired to help others view beyond their current understanding. This concept resonates strongly in the field of software development. When a development team first ventures on a new project, their understanding of the problem the project intends to solve is like observing shadows on the cave wall. They see only the shadows, the simplified and often misleading representations of the complex business processes, systems and challenges. Their initial perceptions are based on assumptions and incomplete knowledge, just like the prisoners interpreting shadows. As the team dives deeper, collaborating closely with business experts, it’s like stepping out of the cave. At first, the depth and complexity of the business processes can be overwhelming. There are new terms to learn and processes to understand. But gradually, just like the freed prisoner’s eyes adapting to the sunlight, the team begins to comprehend the true nature of the domain. They develop a universal language, a shared vocabulary that accurately reflects the reality of the domain, not just its shadows.</p><p><strong>Domain-Driven Design (DDD)</strong> is a software development approach that emphasizes the deep understanding and modelling of the business domain in which a software system operates. Originating from Eric Evans’ book “Domain-Driven Design: Tackling Complexity in the Heart of Software,” DDD is not a new concept by any means, but it remains highly relevant and effective, especially for large and complex systems. Those who have worked with Microservice architectures may have heard of or be familiar with it but in the Salesforce platform ecosystem, you rarely hear it being mentioned. The purpose of this article is to give you a high-level overview that could encourage you to dip your toes in and try to embrace the benefits. Even without fully adopting every aspect of DDD, which is not the intention of this article, its principles can significantly contribute to building a well-architected Salesforce solution that will stand the test of time.</p><p>Before we continue discussing how can this be valuable to you, let’s clarify definitions for the terms we will be using:</p><p><strong>Domain</strong>:</p><ul><li>A domain is the specific area of interest or the subject matter of the software, in this case, the main purpose of the salesforce application you are building. It’s what the solution is all about like customer service, banking or IT service management.</li><li>Domains can further be classified by type:</li><li><strong><em>Core</em></strong>, those that are the focus of the problem(s) you are trying to solve.</li><li><strong><em>Supporting sub-domains</em></strong> are those that enhance the core domain directly but are not the main focus area and that are also not generic. For a core domain of Customer Service, you could need a supporting subdomain of “Surveys and Feedback” for example.</li><li><strong><em>Generic sub-domains</em></strong> are those that are very common to several domains or companies and as the name suggests, generic in nature, these typically reusable services that are not concerned with the core application logic, for example, Logging and Monitoring, Payment or Notifications.</li></ul><p><strong>Model</strong>:</p><ul><li>A model is a simplified conceptual representation of knowledge about the domain, capturing its essential aspects. It will act as a blueprint that guides how the architecture is built around a particular domain in a particular context. Typically represented in a diagram.</li></ul><p><strong>Ubiquitous Language:</strong></p><ul><li>Ubiquitous Language refers to a common and shared language used by everyone involved with the solution, this includes, technical and non-technical team members. Sticking to a particular set of terms and definitions ensures everyone is aligned and there is less confusion and need to translate between business and technical teams.</li></ul><p><strong>Bounded Context</strong>:</p><ul><li>A boundary within which a particular model is defined and applicable. The specific context where certain rules and terms apply uniquely.</li></ul><p>There are additional concepts related to the tactical aspects of DDD such as aggregates, entities, repositories and so on, I have omitted them on purpose to emphasize that to start reaping benefits from DDD you don’t need to deep dive immediately into the details nor fully implement them. DDD is a way of approaching the understanding and definition of a system’s architecture but is also compatible with other architectural approaches.</p><h3>When should we think about domains?</h3><p>In the early phase of a large enterprise project, starting to develop a clear conceptual architecture is an important and useful step which serves as a blueprint for the solution moving forward as this blueprint will be used to communicate how the solution will be structured at the highest level. However, this step can prove to be complex to achieve successfully if approached without a strategy. The complexity of this step can arise due to different reasons, a common reason is that you would typically be dealing with large legacy monolithic systems that are meant to be replaced, these systems are normally not owned and maintained by a single team but by multiple teams, some of these teams may not even exist anymore. The older these systems are, the higher the likelihood that the original intention of those systems has started to get lost, to add to that, there is rarely any valuable documentation. The result is a system landscape that lacks a cohesive end-to-end architecture. The additional reason this can be challenging, is of course, if you are new to or not knowledgeable enough about the domain. In such scenarios, applying Domain-Driven Design (DDD) principles can be beneficial to ensure you start with an accurate model for the solution. With this being said, like in any pattern, this is not something you should apply to all solutions as it can be overkill for smaller and non-complex applications.</p><h3>Understanding the Domain</h3><p>The process of applying DDD in a project begins with a deep and collaborative exploration of the <em>domain</em>. This process involves close interaction with domain experts or in general, those deeply involved in the day-to-day jobs your solution needs to support. If you were working on a Customer Management solution, you would have workshops with Customer Service Managers, Sales Reps., Customer Service Staff and so on. These workshops could be in the form of whiteboarding sessions, event-storming, using the <a href="https://trailhead.salesforce.com/content/learn/modules/jobs-to-be-done-framework-for-designers/learn-about-the-jobs-to-be-done-framework">JTBD framework</a> or some other method that works for you. But note, that these are not traditional requirement elicitation sessions as the focus is not on gathering requirements but on understanding, you would also need to avoid getting into imagining concrete technology solutions at this stage. The goal is to obtain a detailed understanding of their business experts’s jobs and tasks, the challenges they face and their jargon. this activity must include not only a few business experts but also the members of the technical team. This effort is the essence of DDD.</p><h3>One Shared Language</h3><p>This collaborative process naturally leads to the development of a shared language, often referred to in DDD as a ubiquitous language — a vocabulary that is consistently used by the technical team as well as the business experts within a specific context. This language becomes the foundation of the model within that context, ensuring that all discussions, presentations, documentation, and ultimately even the code and configuration reflect the true nature of the domain.</p><h3>Mapping The Landscape</h3><p>While you are working with the business on refining the model of the solution and the subdomains involved, you will start to identify the bounded contexts, this is the area in which a specific model makes sense to those involved in it. Consider an e-commerce business that needs to ship its products. In the e-commerce context, the application would receive “Orders” which represent the customer’s transactions to purchase products, those orders would contain the product IDs, quantities and payment information. The focus in this context is on the customer buying a product from an inventory and its payment. However, in the Shipping context, orders represent Shipping Orders, here we must also manage the aspects of the packaging and physical delivery of the products to the customer. Although, at a conceptual level both are Orders, they have a different purpose in their context. This interaction between different contexts requires careful mapping of concepts and data to ensure a seamless experience and system interoperability.</p><p>To provide an example of how a model and bounded contexts can be communicated. Let’s imagine you are building an IT Asset Management solution which manages the lifecycle of IT Assets from the time they are planned to be procured from vendors, their assignment to employees and finally to disposal. This could be modelled as below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lnwsgizNylNeZiExVQGMUQ.png" /></figure><p>In this model, the company’s key concerns are around Asset Lifecycle Management, this is where most of the intricate business rules would lie in the system which is why this was highlighted as a Core domain, whereas, managing the product catalog has a secondary role and so do the rest of supporting domains. This expresses that most business needs are not around the supporting domains and they may be required mainly to ensure the smooth operation of the Asset Lifecycle. The generic domains are easier to understand, they are essentially generic needs not specific to the business problem but that are still needed for the operation of the system. The arrows in the diagram were used to indicate dependencies.</p><p>You may be wondering if this could have been modelled differently, the answer is yes and this is the exact reason why domain understanding and creating this model with business is an important step, in a complex system is hard to apply general rules as they can vary based on the industry, organization structure and strategy. For instance, based on the findings from the conversations with the business you could conclude that Maintenance and Support could be seen as an entirely separate Context and consider it a Core Domain altogether that interacts with the IT Asset Management.</p><h3>DDD Applied to Salesforce Solutions</h3><p>As an architect defining a Salesforce solution, you will soon realize that having identified the domains and their bounded contexts, will soon start guiding the <a href="https://architect.salesforce.com/well-architected/adaptable/composable">Composability </a>of the design. For example, this could help you to understand if you should propose creating a custom application that handles shipping because this is done in a specialized manner for the business or if you should rather treat it generically and use a third-party product. At a more technical level, it will inform your decisions around the boundaries of an unlocked package as well as its required interfaces and data model entities. Understanding the relationships between bounded contexts will aid in identifying which components should be developed first and which can come after as you will have better clarity on the dependencies between them as they relate to a domain or subdomains.</p><p>When it comes to integration with external services or legacy systems that may not conform to your new architecture, having clear boundaries will help you build an anti-corruption layer to prevent your new system get polluted by the details of the legacy or external system. Domain-driven design works well in tandem with <a href="https://www.salesforce.com/blog/soa-principles/">SOA (Service Oriented Architecture)</a> by helping you define better boundaries and therefore, better service definitions.</p><p>Your newly acquired knowledge will give you deeper insight into the business impact and have a positive effect on the <a href="https://architect.salesforce.com/well-architected/easy/intentional">Intentional</a> aspect of the architecture as it will drive the strategy by informing the prioritization of components and roadmapping of the solution based on the core domain needs. This shift can help developers, especially juniors, to understand the broader context of their work and see beyond code to the real-world problems and scenarios the solution seeks to address.</p><p>The practices and principles in DDD help bring the development team closer to business by making the business feel understood and developers feel engaged. The result is a more manageable, scalable, and effective Salesforce solution that not only meets current business requirements but is also adaptable to future changes and growth, thus maximizing the investment in the platform.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3bddc84fb09b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>