Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Integrating Bounded Contexts - Mini-workshop


Published on

You’re invited to join us for a mini-workshop on Integrating Bounded Contexts with RabbitMQ. We’ll cover the concepts you need to know and we’ll put them to practice in a sandboxed environment (a very simple example PHP project). Some of the topics that will be discussed:

Bounded contexts, domain events, commands, enterprise integration patterns, (de)serialization, (de)coupling, messaging, RabbitMQ.

Published in: Software
  • Be the first to comment

Integrating Bounded Contexts - Mini-workshop

  2. 2. THE DOMAIN == THE PROBLEM SPACE ➤ Domain is divided into subdomains: ➤ Core domain ➤ Supporting subdomain(s) ➤ Generic subdomain(s)
  3. 3. BOUNDED CONTEXTS == THE SOLUTION SPACE ➤ Think “application” instead ➤ Ideally, a bounded context models no more than one subdomain subdomain bounded context
  5. 5. PARTNERSHIP ➤ Succeed or fail together.
  6. 6. SHARED KERNEL ➤ Share part of the model.
  7. 7. CUSTOMER-SUPPLIER ➤ Upstream-downstream relationship.
  8. 8. CONFORMIST ➤ Same as customer-development, but without cooperation.
  9. 9. ANTICORRUPTION LAYER ➤ Provide functionality of the upstream system in terms of your own model.
  10. 10. OPEN HOST SERVICE ➤ There is a (generic) service which can be used by other bounded contexts.
  11. 11. PUBLISHED LANGUAGE ➤ A well-documented, shared language, to allow for translation between models from different contexts.
  12. 12. SEPARATE WAYS ➤ A bounded context has no relation with other contexts.
  13. 13. BIG BALL OF MUD ➤ When models aren’t clearly separated by context boundaries.