1. Event-Driven Architecture advanced

    A platform adopts event-driven architecture broadly and finds debugging and reasoning much harder. When is event-driven the wrong choice?

    2 min answer event-drivencouplingdebuggingobligations
  2. Event-Driven Architecture advanced

    A team proposes routing every internal workflow through an event-streaming platform because it is scalable and decoupled. What questions do you ask and when is a simpler mechanism correct?

    3 min answer event-drivenkafkaover-engineeringtradeoffs
  3. Event-Driven Architecture advanced

    A topic holds 7 days of order events - about 3 TB of unique data at replication factor 3 across 24 partitions on 6 brokers - and has exactly one consumer group, which always reads within a second of the tail. At 14:00 an analytics team deploys a second consumer group configured to start from the earliest offset. What happens over the next hour?

    3 min answer event-drivenpage-cachebackfillquotas
  4. Event-Driven Architecture intermediate

    Before 2017 every consumer of published content at The New York Times integrated with each producing system's own API and bootstrapped its history by calling those APIs. The 2017 publishing pipeline replaced that with one Kafka log. What changed about the cost of adding the eleventh consumer, and about who pays for a backfill?

    3 min answer new york timeskafkaintegration costbackfill
  5. Event-Driven Architecture advanced

    Review this design. Every service publishes one event type per aggregate - OrderChanged carries the whole order document plus a changeType string. Eleven consumers subscribe and each begins with a switch on changeType, ignoring types it does not care about. What would you remove, what would you change, and what would you leave alone?

    3 min answer event-drivenevent granularitycouplingschema