Creating events according to a lightweight Event-driven Architecture is the topic of this post and the second part of: How to drive an Event-driven Architecture for microservices
To recap:
An event is a notable thing that happens inside or outside your business. [1]
An Event-driven architecture (EDA) could be a candidate to realize a communication-basis between microservices and an approach to get the services mostly decoupled. The architectural pattern exist for a couple of years and has been described in papers and articles like [1,2,3].
However in this and the following post I won’t repeat the theory in detail, I’d rather like to describe how to sketch an EDA based system and just sometimes use quotations of the papers above – like [1]:
An event is a notable thing that happens inside or outside your business.
the data backyard 
Du muss angemeldet sein, um einen Kommentar zu veröffentlichen.