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.
On almost every desk on this planet lies a pen and a piece of paper for notes. In the programmers or software-architects world notes are especially technical notes about a component or system – drawn e.g. as UML-sketches on a paper or via an UML tool. However a few minutes and discussions later the names of the UML-boxes are typed into an IDE as part of source-code that will be written during the next days, weeks, months… 
the data backyard 
Du muss angemeldet sein, um einen Kommentar zu veröffentlichen.