Enterprise Architecture Patterns

Domains and Services

A domain groups related business responsibilities. Services carry out particular parts of that work.

Invoicing can sit at the boundary between sales and accounting. Both teams use the information, but that does not mean both should independently redefine the invoice.

Decide which service owns the state and how other domains consume it. Clear boundaries reduce conflicting updates and unclear responsibility.

Sales and accounting may both use invoicing, for example. Make the ownership and boundaries explicit so sharing a service does not leave its data or changes without an owner.