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

The functional aspects of the application tend to get mixed and unwanted side effects creep in.

The boundaries between the layers are too strong which makes modifications harder.

We don't know which layer we're in when modifying a certain class.

The code structure doesn't look good in architecture diagrams.

What's the main problem with organizing code by layer?

What’s the main problem with organizing code by layer?

The architecture becomes less visible because everything is in the same package.

We're mixing the concerns of the web, business logic, and persistence logic.

Everything has to be public because it's in the same package.

We can't use package-private visibility because everything is in the same package.

What's the main problem with organizing code by feature?

What’s the main problem with organizing code by feature?

It makes it easy to express the code in a visual form like diagrams.

It makes it easy to find the code we just talked about at the whiteboard with a teammate.

How does an architecturally expressive package structure help us communicate?

How does an architecturally expressive package structure help us communicate?

Take a quiz to test your understanding of how organizing your code can help you write maintainable software.

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

Quiz: Organizing Code