Blogs

Introducing the Axon Framework IntelliJ plugin

By Mitchell Herrijgers

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

AxonFramework and PostgreSQL without TOAST

By Yvonne Ceelie

When using AxonFramework together with PostgreSQL, you will find out that PostgreSQL uses something that is called TOAST (The Oversized Attribute Storage Technique).

It means that PostgreSQL uses a fixed page size of 8 KB and does not allow for tuples to use multiple pages; Postgres will compress the data. You can find more info about TOAST in the PostgreSQL wiki.  

Introducing The AxonIQ Initializr

By Ben Runchey

Sometimes the most challenging part of any project is getting started. Tasks such as creating the structure for various project artefacts, creating a build file, determining maven coordinates, and picking the right dependency versions can be boring and repetitive. But tragically, Axon Framework isn’t available in the Spring Initializr. So, at AxonIQ, we felt it was high time that we corrected this glaring oversight by providing our very own AxonIQ Initializr just for you, our loyal Axonians!

Sagas in practice

By Yvonne Ceelie

This blog is a how-to implement a Saga with Axon and Spring Boot. Saga’s are a powerful concept but, you need to think about other options before implementing a Saga. You’ll have to keep in mind that the Saga should only orchestrate the process. If you conclude a Saga is the best option, this blog provides some good practices to help you get started.

Revisiting Axon Server in Containers

By Bert Laverman

In my previous blog, I spent just a little bit of text on the challenges of using a single StatefulSet scaled to the number of nodes we want in the cluster. Also, I completely skipped the subject of using Helm to manage the deployment. Both subjects do merit more attention, so let’s do just that.

Distilling the CQRS/ES Capability

By Vijay Nair

CQRS/ES are patterns and to be more specific they are Application Design patterns and their implementation spans across 3 main Architectural areas: structural and continuity, operational and extensibility, and cross-cutting and usability. To help pinpoint the exact implementation areas, let us look at two terms commonly used in Enterprise Architecture - Capabilities and Capability Maps.