<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Domain-Driven Design on Brave New Geek</title><link>https://bravenewgeek.com/tag/domain-driven-design/</link><description>Recent content in Domain-Driven Design on Brave New Geek</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 15 Nov 2024 09:25:32 -0700</lastBuildDate><atom:link href="https://bravenewgeek.com/tag/domain-driven-design/index.xml" rel="self" type="application/rss+xml"/><item><title>Deployment-Driven Development</title><link>https://bravenewgeek.com/deployment-driven-development/</link><pubDate>Mon, 11 Nov 2024 15:57:13 -0700</pubDate><guid>https://bravenewgeek.com/deployment-driven-development/</guid><description>&lt;p&gt;&lt;a href="https://bravenewgeek.com/wp-content/uploads/2024/11/pipeline.png"&gt;&lt;img loading="lazy" src="https://bravenewgeek.com/wp-content/uploads/2024/11/pipeline.png"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Most people use “DDD” to refer to &lt;em&gt;Domain-Driven Design&lt;/em&gt;, which is a useful tool for thinking about API boundaries and system architecture. It provides a way to map a business problem into software. At &lt;a href="https://realkinetic.com"&gt;Real Kinetic&lt;/a&gt;, we regularly help our clients utilize Domain-Driven Design as well as other strategies to architect their systems, avoid some of the pitfalls of DDD, and build an effective foundation for designing software. But &lt;em&gt;this&lt;/em&gt; DDD only speaks to one small aspect of building and shipping software.&lt;/p&gt;</description></item></channel></rss>