liveBook · Manning

Assembly module

As explained in Clean Applications with Hexagonal Architecture

An assembly module wires application components and adapters into a runnable application.

An assembly module wires application components into a runnable system. It is the only module that sees every module; its responsibility is wiring, not application logic. section 6.1

Compile-time boundaries alone do not connect interfaces to implementations at runtime. The assembly uses Spring Boot to discover beans, match interfaces with implementations, and inject dependencies, while the rest of the codebase remains unaware of the framework. section 6.2

Listing 6.1 Parent POM: The hexagonal blueprint
<project>
  <groupId>com.writeflow</groupId>
  <artifactId>writeflow</artifactId>
  <packaging>pom</packaging>
 
  <modules>
    <module>shared-kernel</module>
    <module>application-core</module>
    <module>rest-adapter</module>
    <module>persistence-adapter</module>
    <module>notification-adapter</module>
    <module>spring-boot-assembly</module>
  </modules>
 
</project>
 

The parent POM lists the assembly alongside the core and adapter modules. section 6.1

How Clean Applications with Hexagonal Architecture covers it

How deep it goes
Explains compile-time boundaries and runtime bean wiring, while assigning the assembly no application logic.
Examples
Shows a parent POM listing the assembly and adapters, and an ArticleRepository dependency matched to a persistence implementation.
What you can do after
Operate/configure the assembly module to resolve interfaces to implementations and inject runtime dependencies.
How it connects
Connects dependency injection with ports and adapters by matching interfaces to concrete implementations.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Clean Applications with Hexagonal Architecture. The section links point to the parts of the book it draws on.