Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

8
  • You seem to be using BC to mean "a sub set of my code base" rather than "the language dept A uses to talk about their processes". How are you implementing the BCs? is it just that when you send a message via HTTP you count that as a BC boundary?
    – Ewan
    Commented May 18 at 14:57
  • Mm, interesting. We are implementing BC as isolated parts of our business, that's why I think they are different BC. We offer a CRM-like app, without the need to have a CRM. Nonetheless, we also offer a CRM integration. For the technical setup of the BCs, see my latest update to the Notes section. Commented May 18 at 15:06
  • are they both web apps or does the user download them and run them locally?
    – Ewan
    Commented May 18 at 17:42
  • Both are part of our monolith right now, exposed through a REST API. The user only needs to interact with the RecordsBC api (and we using other back office front ent, setup the integration using both BCs) Commented May 18 at 17:47
  • 1
    Are you asking about DDD? I don't think you have a need for BCs, it sounds like you have one or two apps and they do separate things one BC or two makes no difference. Its not like you have dept 1 says CRM = one thing and dept two says CRM to mean something else
    – Ewan
    Commented May 18 at 19:19