#Kafka
5 notas · última:
The Dual Nature of Events in Event-Driven Architecture
The article argues that events in event-driven systems serve two purposes at once: they trigger actions and carry data. Good event design must keep both the business reason and the changed state in view.
Revisiting the Outbox Pattern
The article revisits the outbox pattern for microservices, explains how it keeps database updates and event publication atomic, and compares it with polling, CDC, 2PC, and other alternatives.
How to Design a Notification System: Frontend + Backend
The post maps a notification system as a five-layer pipeline with backend fan-out, priority handling, idempotency, rate limiting, capacity estimates, and frontend delivery concerns tied to trust and scale.
My company packaged 12 years of my experience into an AI Skill, then laid me off. When it crashed, the CTO called at 5x my salary.
A first-person story about turning years of operational knowledge into an AI Skill, getting laid off, and being called back when the system failed on a newer Kafka setup the skill could not handle.
Understanding concepts in Event Driven Architectures (EDA)
The page explains event-driven architecture as an asynchronous way for system parts to communicate through events, then outlines producers, brokers, consumers, exchanges, and trade-offs.