Get the latest tech news
Falsehoods Software Developers Believe About Event-Driven Systems
When building a distributed system, a common design pattern is to follow the event-driven approach. Event-driven systems can range from a simple in-memory queue to a serverless AWS Lambda with a preceding queue, or even connected Kafka clusters.
When building a distributed system, a common design pattern is to follow the event-driven approach. when reviewing code implementing an even driven architecture, I see common mistakes that cause toil or even operational incidents once deployed to production. Low TPS systems are not subject to backlog Low TPS systems are not subject throttling Processing timeout of XX seconds is sufficient Processing timeout of XX minutes is sufficient Processing timeout of XX hours is sufficient Upstream dependencies' timeouts are properly configured Retry policy is properly configured Event processing time is constant and performance will remain consistent under load
Or read this on Hacker News
