BridgePulse Academy

System Integration Patterns

Event-Driven Sync Between Bounded Contexts

Map domain events to integration boundaries so services stop leaking internal nouns across the wire.

6 weeks Cohort Advanced
Event-Driven Sync Between Bounded Contexts

Overview

When two teams share a database by accident, integrations rot. This module has you publish curated integration events, translate between ubiquitous languages, and document upstream/downstream SLAs with testable stubs. Case studies come from inventory and fulfillment handoffs rather than toy e-commerce.

What you practice

  • Context mapping studio with integration heat map
  • Schema registry walkthrough with compatibility checks
  • Consumer-driven contract tests for async flows
  • SLO drafting worksheet for event lag
  • Poison message handling lab
  • Outbox pattern implementation in a sample service
  • Facilitated critique of a real architecture sketch you bring

Outcomes

  • Publish a versioned event catalog for one domain
  • Run a consumer contract suite in CI
  • Facilitate a cross-team SLA conversation with metrics

FAQ

Labs use Kafka APIs, but concepts transfer to other brokers. Bring your own broker only if you can self-support.