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
Apache Camel
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 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
Prototype sketching with Apache Camel
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 scenarios to integrate several technologies is not done within a few hours, more likely in a couple of days. I.e an architecture or integration prototype would be helpful to verify the ideas and figuring out possible issues and challenges up front. Weiterlesen
the data backyard 