axoniq/axoniq-cookbook

Cookbook with recipes how to prepare Axon applications

Axon Cookbook

Several axon recipes as example of how to tackle specific problems

Code

Under code are the small projects that are used for creating the recipes. Not all recipes might use the same code base (for example use of Spring Boot or no Spring Boot in a recipe). So preferably add to the directory (name) for which recipe the project is used.

Want to adjust one of the recipes or add a new one. Check out the master branch and create your own branch based on it. Add a pull request and request a review. If changes / additions are approved, the change will be merged to master.

Recipes

In the version specific folders are all recipes for the cookbook.

Template for recipes

Under /recipes is a file called 0_asciidoc_axon_cookbook_template.md which contains the template for each of the recipes.

If you change something in the template, make sure each of the recipes are still working accordingly.

Naming

Please name the recipe including the number of the issue. So, for example 11_basic_axon_application_with_spring_boot.md

Issues can be found here: https://github.com/AxonIQ/axoniq-cookbook/projects/1.

Versioning

Make sure in each of the recipes on which version of Axon Framework (and probably other dependencies) the recipe is based.

If a new recipe needs to be created for a newer version of the framework, please create a folder containing the new version number, like version-3.1.X and add the new recipe in this folder. The new recipe can be a "copy paste" from the old recipe but make sure all required steps are adjusted for the new version.

axoniq-cookbook's Issues

Set up for TrackingEventProcessor (including information on how to replay)

Set up application with Spring Boot and Axon Framework

Set up of - one to many events - upcaster

Set up for AxonIQ event store

Convert basic recipe to version 3.1.X

Set up to make use of the Distributed CommandBus

Set up an application using a Saga

Set up of - many to one event - upcaster

Set up for MongoDB event store

How to write an Aggregate test

Create recipe for event processing replays in blue/green

Discussed with @abuijze

Create a recipe template for Ascidoc

Mocking framework

Hi,

hope find you well with this cold call.

I am an author of mocking framework for Kotlin

I see you are using mockito-kotlin.

I just want you to be aware that there is solution that fully supports Kotlin and ask to try it in your new/current projects.

I can help you if you answer to this issue.

Thanks and please star it

Set up to make use of the DisruptorCommandBus

Set up for SubscribingEventProcessor

How to write a Saga test

How to use Metrics

Set up of - one to one event - upcaster

Serialized data in readable BLOB/LOB columns i.o. OID in PostgreSQL

PostgreSQL will by default offload BLOB/LOB entity columns into a private table and reference them with an OID (Object reference ID).
This kills readability of for example the serialized payload of an event when querying the EventStore table directly, something dev/ops personal has to be able to do when debugging an Axon application.

This issue is this to give a recipe how to set up your Axon application, with PosgreSQL and adjust the set up such that the BLOB/LOB data isn't offloaded to another table, but kept in the domain_event_entry table.

For this you should think about adding your own PostgreSQL Dialect to force type descriptions for BLOBL/LOB into for example BYTEA and an orm.xml to override the LOB/BLOB behavior of PostgreSQL.