How APIs and Event driven architecture [...]
summary
Describes an implemented event-driven system that replaces file polling with a publish/subscribe pipeline using Kafka/MQ/Rabbit and microservices that publish lightweight notifications and persist full payloads for reconciliation. Delivery is a two-step event delivery: notify with an event ID, then clients fetch the payload; retention is configurable and reduces missing-file penalties. Operational rules include configurable retries/backoff (typical 3–5 attempts), short timeouts, detailed logging with a global transaction id, OAuth for auth, and a blockchain audit trail for fraud reduction.
AI-written summary · about
chapters (11)
- 0:00Intro
- 2:07Shipping Industry
- 4:07Challenges before digitization
- 7:01Challenges after digitization
- 7:40What is Event
- 9:12Architecture
- 9:32Communication
- 10:02Inventory Architecture
- 16:04Event Delivery
- 18:10Retry
- 20:37Detail logging
related talks
26mEvent Driven APIs
27mGetting started with Event-Driven APis
32mUnifying API and event driven architectures
41mGetting started with Event-Driven Architectures in 2023
31mDemystifying Event-Driven Architectures
27mPatterns for Event-Driven APIs
48mEvent-Driven Architecture – Benefits and Pitfalls
52mSo You Want to Build An Event Driven System?