Link Dump #225

It's Friday! Grab your coffee, take something good to read and enjoy the moment :)

Link Dump #224

One article, two articles, three... and it's Friday so how about one more?

Link Dump #223

What is the best coffee you can have? The one you drink having a book in your hand.

Link Dump #222

What's your mood today? I assume this is a mood for reading :)

Link Dump #221

I assume your New Year's resolutions list may already be full, but how about adding one reading-related?

Link Dump #220

I know this is not a Christmas gift, but I'm sure you will find something for yourself :) 

Link Dump #219

It's reading time! And grab a cup of coffee with you - you might lose track of time!

Link Dump #218

There's still a couple of weeks of reading this year in front of us. Let's use it well :)

Link Dump #217

Every day is good for reading, but Friday is even better :)

So… Which Part of Your System Is Actually Worth Building?

Domain types classification is part of the problem space. It increases our understanding of the business, its priorities, and its main aspects. On the other hand, it is not part of the implementation itself. However, this does not mean it lacks value — it still provides insights that help us make better, more informed software architecture decisions. Let's explore how domain classification can support us in this process.

Link Dump #216

Winter is coming but you shall not be afraid - a new Link Dump is coming too :)

Link Dump #215

Ready for Friday? With a new set of worth reading articles I bet you are :)

Link Dump #214

Another book or maybe a short article? How about both :)

Link Dump #213

I know I do not have to convince you to read but remember that reading improves your focus and memory :)

Core, Supporting, Generic – How to Stop Treating All Domains the Same

Most businesses require knowledge from multiple domains to be successful. Some are essential due to the nature of the business itself, others are mandated by legal regulations and compliance obligations, and some exist simply to meet specific operational requirements.

After the last series of articles, you already know how to identify those domains. But what comes next? Once we define all domains, it’s worth categorizing them. This exercise helps us later make better software architecture decisions and organize teams more effectively.

Link Dump #212

I've got enough reading - said no one ever.

Link Dump #211

Another Friday, another coffee, and more articles to read. Routine does not have to be boring:

Ubiquitous Language in Action: Boundaries Made of Words

You already know what the Ubiquitous Language is and how to define its boundaries. Equipped with that knowledge, let’s return to the Training Center example and clarify what domains and corresponding ubiquitous languages we have.

Link Dump #210

Friday is the perfect day for the reading mood:

Speaking Many Languages in One System

Last time I explained what Ubiquitous Language is, why it is crucial to use it, and how it can support software evolution and maintenance. Today, I would like to share several approaches that can help you define the boundaries of domains within your application.