Summary

We started this chapter by learning about the building blocks that we can use to create a Docker image for the hexagonal system. Then, we created two Docker image types. The first one was based on the uber .jar file, which is used to package and run the application, while the second one was based on native executables, where we could leverage the features Quarkus provides to create a native executable artifact.

Then, we created the Kubernetes objects that were required to deploy the hexagonal system in a Kubernetes cluster. Finally, we deployed the hexagonal system in a local minikube cluster. More than a hexagonal system, we now have a cloud-native hexagonal system ready to tap into the advantages provided by cloud environments.

In the next chapter, we will learn how hexagonal architecture relates to layered architecture, an architectural style used by many applications. Understanding the differences between these two architectures helps us assess which architecture...