Category: Data, Kubernetes, Infrastructure, github

In my previous post I showed you how to run Axon Server locally and configure it for secure operations.

This time around we’ll look at running it in Docker, both using the public image up on Docker Hub as well as with a locally built image, and why you might want to do that. Docker is the perfect platform for running applications in a quick and predictable fashion and we can do that for AxonServer as well. Moving from “plain” Docker towards docker-compose and Kubernetes brings us new challenges, especially with respect to how we deal with storage and a predictable network identity for AxonServer.

For AxonServer Enterprise Edition we use this to deploy a complete cluster and introduce secrets.

Related Articles