The Axon platform offers an innovative and powerful way of sensibly evolving to event-driven microservices. The platform has roots in the well established CQRS (Command Query Responsibility Segregation) and Event Sourcing architectural patterns as well as the DDD (Doman-Driven Design) concepts.

Domain Driven Design (DDD) with Axon

Event Sourcing with Axon Framework

CQRS with Axon Platform

Check out some other Axon related topic on our blog, such as:

Strangling a monolith with Axon server

The process of transforming large legacy monoliths into decoupled, scalable microservices systems is more complex than can be imagined. In this blog we will explain how to strangle a monolith using Axon Server.

Bounded contexts with Axon

Bounded Context is a strategic concept in Domain Driven Design, read here how Axon deals with Bounded Contexts in a few different ways.

Some CQRS and Event sourcing Pitfalls

In this blog you can read about five common pitfalls you need to avoid in CQRS and Event Sourcing systems. Paying insufficient attention to event modeling or to aggregate boundaries, ignoring event serialization, relying on synchronicity, normalizing projections.

How to write an Axon application?

Axon is heavily inspired by domain-driven design (DDD). For an Axon application, this means the following: a clearly separated area of your source code (like a package or sub-project) should be devoted to implementing your domain model, and nothing else.

Subscribe

and find out useful news on Axon releases, invitations to AxonIQ events and other news