A case study on tapping into an existing event-driven architecture using a publish-subscribe model over Kafka. Covers a three-component design — consumer, API, and database — modelled around typed information flow contracts. Includes practical traps to avoid, from parallelism pitfalls to coupling the API and consumer into the same application.