Event Driven Architecture, The Hard Parts : Event Payload

Event Driven Architecture (EDA in short) in an Architectural style where a service publishes an event (think message) which semantically means — something has happened and other services who are interested in the event can react to it by consuming it and execute their business logic against it.

It is one of the architectural styles which is highly scalable, extensible and loosely coupled in nature though there is still some sort of coupling, in the form of the contract of the Event which is published by the Producer.

An event is generally implemented using the Publish Subscribe pattern. The event is published on an Event Broker Topic which is owned by the publisher, and consumers need to listen to this Topic. The consumers are least interested in who is publishing this event. All they care about is reacting to the event whenever it gets published.

That’s all about EDA in short. Let’s come back to our main topic — when you think of the event to be published, you are forced to brainstorm — what should be the payload of this event???

Let’s understand this by a simple business use case —

Yet Another Food Delivery Platform (YAFDP) from Waswani Corp. has gone viral. They have Microservices Architectural Style based application, clubbed with EDA.