Discover Hexagonal Architecture to create web applications with isolated, testable layers. Gain insights into designing clean, maintainable modules and advocating for suitable techniques for your application.

Get Your Hands Dirty on Clean Architecture by Tom Hombergs.png

spring.tar.gz

spring1

spring1-copy

blank

This course will teach you all about creating a web application in the Hexagonal Architecture style. Hexagonal Architecture promotes the separation of concerns by encapsulating logic in different layers of the application. This enables a higher level of isolation, testability, and control over your business specific code. 

You will learn how to design software modules and complete applications in a clean and maintainable manner, while also learning how to advocate for a certain technique given your application and constraints.

By the end of this course, you will have a greater understanding of how to implement software architecture, a key skill for any senior developer.

Hexagonal Software Architecture for Web Applications

Aside from the incoming ports, for certain use cases, we might want to skip the application layer as a whole, as the figure below shows.

# Skipping application services


Here, the `AccountPersistenceAdapter` class within an outgoing adapter directly implements an incoming port and replaces the application service that usually implements an incoming port.

It is very tempting to do this for simple #key# CRUD: Create, Read, Update, Delete #key# use cases, since in this case, an application service usually only forwards a create, update, or delete request to the persistence adapter, without adding any domain logic. Instead of forwarding, we can let the persistence adapter implement the use case directly.

# Shared model

This, however, requires a shared model between the incoming adapter and the outgoing adapter, which is the `Account` domain entity in this case, so it usually means that we're using the domain model as the input model as described above.

# Complex use cases



Learn why you should consider skipping application services in certain use cases.

Before We Begin

What's Wrong with Layers?

Inverting Dependencies

Organizing Code

Implementing a Use Case

Implementing a Web Adapter

Implementing a Persistence Adapter

Testing Architecture Elements

Mapping Between Boundaries

Assembling the Application

Enforcing Architecture Boundaries

Taking Shortcuts Consciously

Assessment

Conclusion

Appendix

Skipping Application Services

Skipping application services