Practical DDD in TypeScript: Domain Service

The story about DDD in TypeScript continues by presenting the first stateless pattern in this series — Domain Service.

Photo by Kate Townsend on Unsplash

I don’t have official statistics about naming code structures, but let us be honest — we are developers, and we name our classes… almost well, mostly awfully. In most cases, we provide some almost-unique names and attach some suffixes.

Names can be different: User, Account, Registration… Options are indefinite. But, suffixes are finite, and in most cases, they are: Entity, Repository, Factory, Service…

Join Medium with my referral link - Marko Milojevic

Other articles from DDD series:
1. Practical DDD in TypeScript: Why Is It Important?
2. Practical DDD in TypeScript: Value Object
3. Practical DDD in TypeScript: Entity

Golang Blogs

Yes, Service! I believe that is the most common suffix everywhere, it doesn’t matter if we use DDD or any other pattern at all. In many cases, Service is simply used for anything which we can’t name anyhow better.

Service is probably one of the most misused DDD patterns. Misunderstanding about Domain Service’s purpose comes from many different web frameworks, where Service is everything.

Disclaimer: Effective September 1st, 2023, the referral system on Medium
is no longer operational. If you appreciate this DDD series and would 
like to endorse the efforts of both myself and fellow authors on Medium, 
kindly demonstrate your support through claps, follows, or comments on 
our blogs. Your consideration is greatly appreciated. Thank you in advance!

But what is the actual purpose of the Domain Service? And how it differs from other Services that…