Doing more with less: Part 2 - Buy don't build using DDD
This is the second article in a series of articles that describe how engineering leaders do more with less in the post-zero interest rate era. The other article in the series is:
In this article, I describe another strategy: buying parts of your application rather than building them. There are various ways to buy parts of your application ranging from an open-source library to a SaaS service.
There are a couple of different ways to identify those parts of your application that you should buy rather than build. In this article, I’ll describe how to use Domain-Driven design (DDD) (sub)domain types to make build vs. buy decisions. In a later article, I’ll cover Wardley mapping. Let’s start by defining what is meant by a DDD subdomain.