Using Microservices in an Event-driven Architecture offers the possibility to use Complex Event Processing in a lightweight context.
Please find my new article Event-driven Microservices & Event Processing on the codecentric blog.
Event Driven Architecture
Event Generator – a simple approach
This is the third part of: How to drive an Event-driven Architecture for microservices and it covers the first code-sketch to create an event generator based on Spring Boot and Apache Camel.
Weiterlesen
How to drive Event Generation
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]
How to drive an Event-driven Architecture for microservices
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.
How to split a monolith and legacy code via code-sketches
Legacy-code monoliths are one of these challenges which lead often to controversy discussions and questions like:
- What are the pros and cons of getting rid of the code-base?
- How to get rid of it, via a big-bang or splitting it step by step?
- What are the efforts?
In this post I’d like to describe a way how to create the first code-sketch which could lead to an insight into the possibilities to tackle the beast step by step. Weiterlesen
the data backyard 
Du muss angemeldet sein, um einen Kommentar zu veröffentlichen.