Announcing Axon Server 2025.0: Connecting to Axon Server made easy

AxonIQ is a company known for making Event Sourcing easy. This is why we’re happy to announce the launch of Axon Server 2025.0, which now includes robust support for bi-directional HTTP connections for all of your event-sourced applications. This literally means that you can now use any programming language to interact with Axon Server. This capability was originally called AxonIQ Synapse, but its previous implementations required developers to download an additional executable to run along with their Axon Server. Now, a fully embedded and configurable HTTP server is available within Axon Server 2025.0, so let’s talk about the implications of what that really means.

My persistent storage has its own web server; does yours?

When building today’s applications and services, developers have various options to choose from for their persistent storage, such as relational databases, no-SQL databases, and of course, event stores (like Axon Server). With Axon Server 2025.0, developers can quickly configure an HTTP endpoint within Axon Server for their application context and then use it to store and consume all message types supported by Axon Server (such as Events, Commands, and Queries).

The video below shows how to register a new HTTP (or RSocket) endpoint, specify the context, and set any additional properties.

Creating Event-Driven systems with 3rd parties has never been easier

So, needless to say, the implications are huge! This means your event-driven applications no longer need to be written in 100% Java (or use JVM-based languages). Think about it from this perspective. Let’s say that you have a SAAS (software as a service) or PAAS (platform as a service) business model, and to get your service off the ground and working quickly, you’ve decided to partner with a few 3rd party solutions that simplify operations that you currently don’t do yourself.

Connecting a JVM-based Axon application with non-JVM Axon applications.	Connecting non-JVM Axon applications with each other

For example, if you’re building an Axon application in the financial services domain, it could be that you’ve selected a 3rd party solution for fraud detection. Now, what are the chances that every partner you use also uses the same programming language you prefer? With Axon Server 2025.0, this doesn’t matter. As shown in the video above, implementing this is quite easy. Here's how the process would work.

• By default, no endpoint for the 3rd party partner is defined, so you create one for your context as shown in the video above.

• You further specify a webhook URL through which your 3rd party partner will be notified when specific Events occur, such as financial transaction events.

• Your 3rd party partner uses their preferred language (such as Python, JavaScript, Go, etc.) to write an Event Handler that receives financial transaction events via the webhook URL. Within their internal systems, they process the events to determine if any fraudulent activity has occurred.

• Your third-party partner detects unusual activity and uses the Axon Server Integration API to send a Command via HTTP to the Axon application, which will then act upon fraudulent activity, e.g., suspending an account.

Yes, this means that your 3rd party solutions providers can create Command or Query messages and easily send them to Axon Server over HTTP or RSocket. And guess what’s the best part? Axon Server 2025 also provides the capability of streaming events over supported transports, so there’s no need to deploy your own token store, thanks to the built-in Persistent Stream feature. This means you can monitor and control your event streams directly from the admin interface.

In addition to embedding an HTTP server, Axon Server 2025.0 also includes support for the RSocket protocol, which gives bi-directional communication between servers while maintaining a persistent connection.

Wrapping Up

Axon Server 2025.0 is officially here, and we think this will open the door for all organizations to create event-driven applications, regardless of their preferred programming language and environment. The roadmap for 2025 is packed and will have more exciting features coming later in the year. We’re ensuring that live webinars, videos, documentation updates, and blog posts will help you to get the most out of Axon Server 2025!

Looking for help on jumpstarting your Event-Sourced app with Axon Server? Feel free to use this form to book a chat with one of our solution architects to let us know what you’re working on. We’ll be happy to show you step-by-step on getting your project off the ground. We’re happy to help your organization adapt to Event Sourcing, so feel free to contact us!