RE: Small sizing BC into multiple BCs

Hi there,

from my point of view it is a good approach, I used to hardly separate BCs using (in .net) different assemblies (packages in a java world) and generally hosting them on different endpoints (services) so that communication between BCs is forced via some sort of web/rest/soap calls or bus commands/events and the UI (web or whatever) is a "mere" UI composition system that connects/collects information and commands/tasks exposed by the various BCs.

.m

From: [email protected] [mailto:[email protected]] On Behalf Of Jose Fernandez
Sent: domenica 6 ottobre 2013 03.42
To: [email protected]
Subject: [domaindrivendesign] Small sizing BC into multiple BCs





How are you doing?
I am working on a project where I have a Marketing System Domain.
I have the following sections in mind (think of a menu)
Home (sort of a dashboard)
Prospects (People opting in in sales pages, the whole CRM deal I would say)
Calendar (All related to add task and events to a calendar)
Email System (Something like AWeber in a minimal scale)
Analytics (Some stats on how your emails, landing pages and other tools are performing)
Account (all your account information, name, password, payment info, etc)
Help (FAQ)
So, when I look at other systems, let's say, e-commerce websites, Marketing is on its own a Bounded Context. Now, I don't feel like making of my system a melting pot by adding these concepts together.
So, I think I can make smaller BC and separate a little bit all these features.
For example, Prospects would be CRM, Calendar/Tasks could be Scheduling, Email System its own BC, Analytics its own, Account and SignUp/SignIn into Membership
Is that a good approach?