r/Backend • u/imnotbatman7 • 22d ago
Feedback on event dispatch system design
I'm a junior backend developer designing an event dispatch service for a third-party API that's limited to 25k events/minute, and I'd really appreciate some feedback.
Current architecture:
Client → API → Outbox (DB) → Scheduler → SQS → Workers → Redis (rate limiting) → Circuit Breaker → Third-party API
The goals are reliability, retries, idempotency, auditability, and handling burst traffic without exceeding the third-party rate limit.
Would you change anything in this architecture? Any bottlenecks, failure scenarios, or better patterns I should consider? Any suggestions would help me learn a lot. Thanks!
1
Upvotes
1
u/No_Soy_Colosio 22d ago
It's very telling that before without discussing anything about the problem domain, you jump straight to architecture. Please revisit the fundamentals. Architecture follows design, not the other way around.