Software developers should never do the same thing twice a day. They are paid to automate things in an intelligent way. This also increases quality, because the repetitive task is always done exactly the same way. But sometimes it is quite hard to automate something 🧐.
Axon.ivy 7.0
I'm secretly thinking of an Axon.ivy Engine 7.0 🙃. Here I see the former classic Windows approach. Software has to be installed by hand and configured in an administration interface (Admin UI). To automate such an installation means quite hard work, because Axon.ivy 7.0 was not designed for that at all - the configuration was in the system database. So you had to download the engine, install it, start the system database creation and then manually fill the right tables with the right queries in the database 😬. Very tedious and there is the risk that with each new release of Axon.ivy the automation will break! The complexity of this procedure led us to miserably long installation documents of Axon.ivy Engine installation - instead of replacing the documentation with a script (automation).
Docker as the initial driver
Docker 🐳 has changed the world (at least for me). As of now, a system administrator job is something much more interesting to me. Controlled and isolated installation, which can be reproduced exactly the same on any machine.
We thought we have to be able to do that with the Axon.ivy Engine too 🚀! To run an Axon.ivy Engine efficiently in Docker, the installation must be easy to automate. Therefore, we need to bring the configuration from the database into a file. Files are perfect to automate something. You just need to be able to do a COPY
to the right place. That's how the ivy.yaml
was created and later the app.yaml
.
So this feature is not only for Docker. Docker was only the driver. You now can automate the hole Axon.ivy Engine Setup for Windows and Linux without using Container Technology. Do it!
Blog
This was my blog post number 1⃣ . New ones will follow 😉. Please let me know if you want to read something about a special topic. Feedback for this post is also much appreciated.