How to expressively represent (database, validation and unexpected) errors as domain concepts using functional programming concept...

Domain-Driven Design is the approach to software development which enables us to translate complex problem domains into rich, expr...

In this article, we discuss how we can use a few CQS principles to handle unbounded 0-to-many or many-to-many collections in aggre...

In this series, we answer common questions in aggregate design. Here's an article orignating from the question, "How can a domain ...

In this article, you'll learn how identify the aggregate root and encapsulate a boundary around related entities. You'll also lear...

An intention revealing interface is a standard for writing code that is expressive enough to adequately explain it's purpose witho...

In this post, I explain how good ol' fashioned encapsulation + TypeScript getters and setters enable us to effectively create Doma...

There are several patterns that we can utilize in order to handle data access concerns in Domain-Driven Design. In this article, w...

Entities are the first natural place we should aim to place business logic in domain-driven applications. In this article, we talk...

A comparison between designing Node.js applications using REST-first design and Domain-Driven Design.

This is how and why I took upon myself the hellish task of migrating an existing Sequelize + TypeScript application to use UUIDs i...

Value Objects are one of the primary components of Domain-Driven Design. Here's a simple Value Object class in TypeScript.