Navigation variant: B7-4 GROUPED dropdowns (Programs, Company, Resources)

API Integrations · Advanced

Event-Driven Integration Patterns

Live online · 5 weeks · 17 live hours

Walk through choreography vs orchestration with concrete failure injections. You'll sketch sagas for a loyalty points system and discuss when to prefer synchronous fallbacks—common in Korean payment ecosystems with strict latency budgets.

Tuition (informational)

₩720,000

No checkout here—request details via Contact. See Money-Back Policy.

Message queue architecture sketched on a glass whiteboard
Portrait for lead mentor Jun Lee

Jun Lee

Kafka-focused engineer; runs break-fix labs on consumer lag.

What you build and discuss

  • Outbox vs inbox tradeoffs with code sketches
  • Partition key design lab to avoid hot shards
  • Tracing headers across bounded contexts
  • Compensation workflows with human checkpoints
  • Load tests that reveal consumer lag scenarios
  • Documentation patterns for async APIs

Outcomes we assess

  1. 01 Diagram an event flow with explicit failure compensation
  2. 02 Choose between topic-per-team vs event-type topics with rationale
  3. 03 Demonstrate trace correlation in a sample stack

Participant notes

“Event-Driven Integration Patterns made saga compensation click. The loyalty points case was oddly specific—in a helpful way.”
— Ivy , Software engineer

Logistics & candor

Includes a limitation-focused FAQ item per program requirements.

Core examples use Kafka concepts; mapping to Pulsar or SNS/SQS is discussed in office hours.