axoniq/dev-portal-utterances

dev-portal-utterances's Issues

Distilling the CQRS/ES Capability

en/-/revisiting-axon-server-in-containers

Revisiting Axon Server in Containers - AxonIQ Developer Portal - AxonIQ

In my previous Blog on running a containerized Axon Server, 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.

https://developer-next.axoniq.io/en/-/revisiting-axon-server-in-containers

Revisiting Axon Server in Containers

Protect sensitive data in an Event-Sourced Application

w/sagas-in-practice

Sagas in practice

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.

https://developer-next.axoniq.io/w/sagas-in-practice

Dispelling the Eventual Consistency FUD when using Event Sourcing

en/-/set-based-consistency-validation

Set Based Consistency Validation - AxonIQ Developer Portal - AxonIQ

Requests like “How do I ensure the email address in a User aggregate is unique?” or “How do I ensure usernames are only used once on command handling?” reach us quite often. We can rephrase them: How do I consistently validate consistency among a set in such a system? None of these are Axon-specific problems, really, but more so issues you would encounter when using CQRS in combination with Event Sourcing. Due to this, they crop up when using Axon Framework. Before diving into how to tackle this with Axon, let us first explain the problem we face here.

https://developer-next.axoniq.io/en/-/set-based-consistency-validation