How to drive Event Generation

Event generation resp. announcementCreating 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]

Continue reading “How to drive Event Generation”

How to drive an Event-driven Architecture for microservices

Event-driven Architecture logoAn 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.

Continue reading “How to drive an Event-driven Architecture for microservices”

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. Continue reading “How to split a monolith and legacy code via code-sketches”

Application and system sketching based on code templates

book-731199_1280On 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… Continue reading “Application and system sketching based on code templates”

SOLID Sketching

Writing code to sketch the first core feature of an application could lead to a point where the next feature has to be realized roughly, too – just because of trivial dependencies. The code-base grows and when you are unlucky the overview of the sketches gets lost. However keeping the code-base clean and open for the future has to be a goal and can be achieved by applying the SOLID principles. Continue reading “SOLID Sketching”

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. Continue reading “Prototype sketching with Apache Camel”