Different than usual, upgrading to Axon Framework 4.7.x may just impact your application. For that, we want to extend our apologies, as this differs from our desired approach towards minor releases. This blog describes several upgrade scenarios, like what you need to do when you want to move to Jakarta or stay on Javax. Each scenario provides a list of actions to upgrade to 4.7 to guide you.
Repositories are essential components in Axon Framework. However, they mostly remain behind the scenes, and developers don't need to interact with them directly. Usually, the framework can configure, instantiate and use the correct repository based on how the developer has constructed the domain components. That convenience sometimes leads to misunderstandings. Those are caused by the many meanings of the term "repository" and the assumptions developers make when they hear or read it.
A comparison of Apache Kafka and Axon Server with respect to how they work as message pipe. Will go through the format used and how sending messages work. As well as how messages are routed and how the solutions scale.
Because set-based consistency validation is a hot topic, we discuss it a lot within AxonIQ. In one of these discussions, my colleague Frédéric Gendebien proposed applying the actor model to solve this problem. Here is how it helps validate the uniqueness of a specific value against a set.
Support for the `jakarta` namespace in Axon Framework 4.6
By Milen Dyankov
Friday, October 07, 2022
A significant change in the Java Enterprise space was made a few years back. The javax package was replaced with the jakarta one. As some Axon features use the JPA and JTA specifications, we needed to addopt the change. Here is how we did it in Axon Framework 4.6