https://medium.com/wix-engineering/event-driven-architecture-5-pitfalls-to-avoid-b3ebf885bdb1
https://medium.com/wix-engineering/troubleshooting-kafka-for-2000-microservices-at-wix-986ee382fd1e
Events Payloads
Fat Payloads → Less coupling, Time Sensitive, Higher Bandwidth Cost.
- The subscriber doesn’t need to hit any endpoint to get further information while processing the event (less coupling between publishers and subscribers).
- The data in an event could be outdated by the time it is processed.
Thin Payloads → More coupling, Real-Time, Lower Bandwidth Cost
- Thin Events shine when the real-time information is crucial at the time of processing.
- Usually is necessary that the subscriber hit one or more endpoints to get further information related to the received event (add coupling between publishers and subscribers)
https://codesimple.blog/2019/02/16/events-fat-or-thin/
https://www.notapenguin.blog/posts/rust-event-systems/