Event-driven architecture with Kafka: the parts that actually bite you
Topics, partitions, consumer groups, ordering, idempotency and dead-letter queues: the Kafka concepts that decide whether an event-driven system stays correct under load.
✦ Writing8 posts
scribbled between deploys
Practical write-ups on AI engineering, event-driven systems, data pipelines and shipping to production: the trade-offs, the failure modes and the code.
Topics, partitions, consumer groups, ordering, idempotency and dead-letter queues: the Kafka concepts that decide whether an event-driven system stays correct under load.
Modelling a migration as a DAG: chunking, retries with backoff, checkpoints, idempotent writes, backfills and verification, all running as Argo Workflows on Kubernetes.
Where the milliseconds go in a voice agent, and how streaming, voice activity detection, barge-in and a latency budget make a conversation feel natural.
Designing role-based access control that survives growth: permissions over roles, short-lived JWTs with refresh-token rotation, and mapping app roles to cloud IAM.
Cache-aside, write-through and TTL strategy, plus the failure modes that hurt in production: stampedes, stale data and invalidation, with code.
Rolling updates, blue-green and canary releases, readiness probes and graceful shutdown on Kubernetes, and how to get the same guarantees on one VM with PM2 and Nginx.
Golden sets, offline evals, LLM-as-judge and its pitfalls, and the online signals that tell you whether an AI feature actually got better.