Engineering notes
RSS ↗Blog
Design patterns for multi-provider APIs: a payments case study
How to integrate M-Pesa, Stripe (US & UK) and Paystack behind one clean interface using the Adapter, Registry and Facade patterns — with TypeScript examples, diagrams, the bad code to avoid, and what bad design costs the business in delivery speed and dollars.
System DesignDesign PatternsPaymentsTypeScriptAPIsDesigning idempotent payment APIs that never double-charge
A practical guide to exactly-once payment semantics — idempotency keys, request fingerprints, and the database patterns that make retries safe.
PaymentsDistributed SystemsAPIsFive lessons from running event-driven systems in production
Hard-won lessons on Kafka, eventual consistency, idempotent consumers, and observability from building event-driven platforms at scale.
Event-Driven ArchitectureKafkaDistributed Systems