<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Otavio Santana on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/authors/otavio-santana/</link><description>Recent content in Otavio Santana on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 18 Nov 2025 07:00:01 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/authors/otavio-santana/index.xml" rel="self" type="application/rss+xml"/><item><title>Strategic Domain-Driven Design: The Missing Link in Modern Java Projects</title><link>https://javapro-en.svenruppert.com/strategic-domain-driven-design-the-missing-link-in-modern-java-projects/</link><pubDate>Tue, 18 Nov 2025 07:00:01 +0000</pubDate><guid>https://javapro-en.svenruppert.com/strategic-domain-driven-design-the-missing-link-in-modern-java-projects/</guid><description>&lt;p&gt;Many developers believe they are applying Domain-Driven Design (DDD) when, in reality, they are focused almost exclusively on &lt;a href="https://javapro.io/2025/07/01/mastering-the-basics-of-domain-driven-design-with-java/"&gt;tactical implementation&lt;/a&gt; — aggregates, repositories, and services — while overlooking its foundational layer: Strategic Design. This initial misstep has cascading consequences. Starting in the wrong step had several implications, such as a lack of understanding of the business and its strategic priorities, which causes teams to fail to align their solutions with real-world needs. Terminology becomes inconsistent, reflecting implementation details rather than domain insights. This lack of clarity opens the door to unnecessary Complexity, misaligned abstractions, and ultimately, brittle systems that fail to deliver business value. Strategic DDD is not optional; it is the discipline that anchors the entire design effort to the organisation&amp;rsquo;s purpose.&lt;/p&gt;</description></item><item><title>Mastering the Basics of Domain-Driven Design with Java</title><link>https://javapro-en.svenruppert.com/mastering-the-basics-of-domain-driven-design-with-java/</link><pubDate>Tue, 01 Jul 2025 07:00:01 +0000</pubDate><guid>https://javapro-en.svenruppert.com/mastering-the-basics-of-domain-driven-design-with-java/</guid><description>&lt;p&gt;Domain-driven design (DDD) is a critical approach in software development, yet its essence often gets buried under layers of complexity and misunderstanding. At its core, DDD aims to align software design with the needs of the business or stakeholders, ensuring that what we build addresses real problems. Even that sounds like a cliche in software development, and obviously, it is still a challenge to most organizations.&lt;/p&gt;
&lt;p&gt;One standout example is &lt;em&gt;Forbes&amp;rsquo; 16 Obstacles to a Successful Software Project&lt;/em&gt;, which emphasizes challenges such as hyper-focused planning, unclear expectations, and poor collaboration. These issues often lead to scenarios where software is more about managing complexity than solving problems.&lt;/p&gt;</description></item></channel></rss>