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.
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. The example used in this series of posts is: A user does a purchase in an e-commerce shop and wants to get an … Continue reading Event Generator – a simple approach
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.  The following example could be a notable thing in our business and … Continue reading How to drive Event Generation
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 … Continue reading How to drive an Event-driven Architecture for microservices
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 … Continue reading How to split a monolith and legacy code via code-sketches
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 … Continue reading Application and system sketching based on code templates
Almost every new project contains legacy code, legacy components or systems. Besides the business-logic a lot of boilerplate code has to be created; only to realize the integration of the legacy parts. Additionally at the beginning of a project it is not clear if the chosen approach works to integrate the legacy components. Coding different … Continue reading Prototype sketching with Apache Camel
A few months ago I got in touch with Kafka – the message broker Apache Kafka rather than Franz Kafka the novelist. Apache Kafka is simply a message broker which claims to be: Fast – Hundreds of MB r/w per second from thousands of clients Scalable Central data backbone – Data streams are partitioned and … Continue reading A coffee with Kafka