Deepening Our Open Source Commitment

Today we are very proud to announce that we are open sourcing most of the functionality previously available in AxonDB and AxonHub into a unified platform - AxonServer. We are also realigning the Axon Framework towards AxonServer and offering a new simplified, combined platform named Axon 4.0.


Introducing Subscription Queries

Subscription Queries are a new feature of Axon Framework 3.3. In this blog, we'll examine why they were introduced and how to use them.


Event Sourcing vs blockchain

Axon Framework enables developers to easily write Java applications using Event Sourcing. At a first glance, Event Sourcing has important similarities to the popular blockchain paradigm. As a result, we regularly get questions about how they relate. In this blog, we'll explore their similarities, differences, and potential combinations.


Building Reactive Systems with Axon Framework

We all know what defines a reactive system. This blog post highlights how Axon Framework fits in building one.


Running AxonHub and AxonDB on Kubernetes - part 1

A quickly increasing number of Axon Framework users are deploying their applications to Kubernetes. The easiest way of creating an Axon-based microservices system on Kubernetes is to use the full Axon stack of Axon Framework, AxonHub and AxonDB. In this blog, we'll explain how to run AxonHub and AxonDB on a Kubernetes cluster.


The intelligent message routing platform

AxonHub delivers the intelligence to route events and other messages correctly and efficiently, in complex microservices landscapes.


A message’s journey through Axon Framework

Starting with Axon Framework is easy, follow one of the excellent live coding webinars, listen to one of the available recordings, or start with one of our coding recipes. Most likely, you'll have a small application running with Axon Framework in no time. This blog explores how Axon Framework calls your components precisely.


The business case for event sourcing

Conferences, meetups and Twitter are buzzing about “event sourcing” (ES) these days. The concept often gets linked to domain-driven design (DDD), which has some merit but is not the essence. Also, it sometimes gets placed in a highly technical context.


It’s not just about events!

We hear a lot about event-driven architecture these days, especially in the context of microservices. For instance, Gartner has identified this as one of the top 10 technology trends for 2018.


How do I enhance events with data that is not part of the Aggregate?


How can I identify entities within an aggregate?

I have an entity in my aggregate, which the aggregate root has a one-to-many relationship with. If I want to target one of these entities in a command, how do I best identify it?

Sign up for our newsletter

monthly updates about new product releases and invitations to AxonIQ events