Microservices

Microservices is a distinctive architectural style that has become popular in recent years as businesses aim to become more agile. The Microservices approach breaks development down into manageable segments, improving efficiency and reducing the time required for new deployments. Microservices architecture is trendy for greenfield development projects, but it can also be applied to traditional applications post-launch.

Introducing the Axon Framework IntelliJ plugin

By Mitchell Herrijgers

    5 min

|

    Mar 11, 2022

AxonIQ is introducing an IntelliJ plugin to make developing applications with Axon Framework and Axon Server even easier!

Dispelling the Eventual Consistency FUD when using Event Sourcing

By Vijay Nair

    6 min

|

    Mar 24, 2021

In the CQRS/ES space, we are equally guilty of not countering the FUD with enough examples and literature that gives relevant data points for folks wanting to adopt these patterns. What if I told you that your systems built with CQRS/ES are as transactionally consistent as systems built without these patterns using the more formal storage methods! Well, let’s walk through an example actually to prove it.

Event Store Migration and Conversion - How to move or transform events in bulk

By Bert Laverman

    11 min

|

    Dec 21, 2020

There are several situations where you might want to copy or move the contents of your Event Store, not just to build a view model, but to either move events to a new system or perform large-scale conversions on the contents. In this blog, we will look at some of the scenarios and the different approaches available.

From Model to Code - Zoom Out

By Sara Torrey   &   Ivan Dugalic

    6 min

|

    Dec 14, 2020

In the previous blog post, this one will help to visualize how multiple software systems fit together within the bounds of an enterprise.

Split & Merge Fundamentals

By Milan Savić   &   Sara Pellegrini

    7 min

|

    Nov 26, 2020

Nowadays, systems must be designed to handle loads that change quickly and dynamically. In these situations, it is expected that our applications adapt accordingly. Axon is capable of parallel and distributed event processing. It uses segmentation to separate the event stream and then processes those segments in different threads, which may be located in different JVM; therefore, achieving distributed processing. 

From Model to Code - Translating the (Event)Model into Code

By Ivan Dugalic

    6 min

|

    Nov 24, 2020

Following the previous blog post, this one will focus on translating the event model to the source code, by using Axon Framework as a programming model and Axon Server as an event store and message broker.

Strangling a monolith with Axon Server

By Yvonne Ceelie

    4 min

|

    Mar 08, 2019

The process of transforming large legacy monoliths into decoupled, scalable microservices systems can be very complex. This blog describes an approach on how using  Axon Server with the strangler pattern can help simplify this process and speed up the delivery time. 

Building Reactive Systems with Axon Framework

By Milan Savić

    5 min

|

    Jul 18, 2018

Unfortunately, old systems aren’t as responsive as we expect them to be. They cannot be scaled that easily. Instead, they use processor time, waiting for operations to complete when they could do something else (processing another request, doing some background calculations, etc.). In this blog, we will discuss why Axon Framework provides infrastructural components that help us build reactive systems.

A message’s journey through Axon Framework

By Steven van Beelen

    2 min

|

    Dec 19, 2017

In your application, you probably have created a couple of components: client code that issues commands; a command handling component; an event handling component. But how does Axon Framework call these components precisely? This blog provides a representation that addresses this question.