CODEWITHSUNDEEP
nservicebussoa
theother
theother

Reputation: 53

NServiceBus & deciding service boundaries

I am a beginner at NSB and I have been looking for some kind of rule of thumb for deciding what constitutes as a separate service. Unfortunately I haven't found much online or in David Boike's book or on the docs page.

The typical examples given are Sales, Shipping, Billing. So my original thinking is to divide according to real departments in a company, but what about things like Logging and other things that may fit into a 'fire and forget' model? Wouldn't having so many services increase the complexity? Is there a certain optimal number?

what is a good rule of thumb for deciding what is a real service without going over the top?

Upvotes: 2

Views: 165

Answers (1)

Udi Dahan
Udi Dahan

Reputation: 12057

Logging, security, and many other "cross-cutting" concerns are usually put together in an "IT/Ops" Service.

UI color schemes and layout are the responsibility of a Branding service.

Beyond that, it can be quite hard to find the right boundaries for services. Organizational structure can be tempting, but it is rarely precise - this being due to the relatively large amount of overlap in business responsibilities between departments.

Here's a video that might help give some more insight:

http://www.udidahan.com/2015/02/02/finding-service-boundaries-%E2%80%93-illustrated-in-healthcare/

Upvotes: 3

Related Questions