Adding Quarkus to a modularized hexagonal application

To recap, we structured the topology and inventory system in three modularized hexagons:  Domain, Application, and Framework. A question that may arise is: Which module should be responsible for starting the Quarkus engine? Well, to avoid blurring the responsibilities of each module in the topology and inventory system, we'll create a dedicated module whose sole purpose will be to aggregate the other hexagonal system modules and to bootstrap the Quarkus engine. We name this new module Bootstrap, as illustrated in the following diagram:

Figure 10.4 – The bootstrap aggregator module

The bootstrap module is an aggregator module that provides, from one side, the dependencies required to initialize Quarkus and, from the other side, the hexagonal module dependencies to be used in conjunction with Quarkus.

Let's create this new bootstrap module in the topology and inventory system...