Category

event driven architecture

7 articles across 2 sub-topics

Stream Processing Pipeline Pattern: Stateful Real-Time Data Products

Stream Processing Pipeline Pattern: Stateful Real-Time Data Products

TLDR: Stream pipelines succeed when event-time semantics, state management, and replay strategy are designed together — and Kafka Streams lets you build all three directly inside your Spring Boot service. Stripe's real-time fraud detection processes...

14 min read

Serverless Architecture Pattern: Event-Driven Scale with Operational Guardrails

TLDR: Serverless is strongest for spiky asynchronous workloads when cold-start, observability, and state boundaries are intentionally designed. TLDR: Serverless works best for spiky, event-driven workloads when you design for idempotency, observabili...

12 min read

Integration Architecture Patterns: Orchestration, Choreography, Schema Contracts, and Idempotent Receivers

TLDR: Integration failures usually come from weak contracts, unsafe retries, and missing ownership rather than from choosing the wrong transport. Orchestration, choreography, schema contracts, and idempotent receivers are patterns for making cross-bo...

14 min read

Event Sourcing Pattern: Auditability, Replay, and Evolution of Domain State

TLDR: Event sourcing pays off when regulatory audit history and replay are first-class requirements — but it demands strict schema evolution, a snapshot strategy, and a framework that owns aggregate lifecycle. Spring Boot + Axon Framework is the fast...

15 min read

Dead Letter Queue Pattern: Isolating Poison Messages and Recovering Safely

TLDR: A dead letter queue protects throughput by moving repeatedly failing messages out of the hot path. It only works if retries are bounded, triage has an owner, and replay is a deliberate workflow instead of a panic button. TLDR: The main SRE ques...

14 min read

Change Data Capture Pattern: Log-Based Data Movement Without Full Reloads

TLDR: Change data capture moves committed database changes into downstream systems without full reloads. It is most useful when freshness matters, replay matters, and the source database must remain the system of record. TLDR: CDC becomes production-...

15 min read