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

## How does this help me build maintainable software?

The Hexagonal Architecture style cleanly separates between domain logic and outward-facing adapters. This helps us define a clear testing strategy that covers the central domain logic with unit tests
and the adapters with integration tests.

The input and output ports provide very visible mocking points in tests. For each port, we can decide to mock it or to use the real implementation. If the ports are each very small and focused, mocking them is a breeze instead of a chore. The less methods a port interface provides, the less confusion there is about which of the methods we have to mock in a test.



# How does this help me build maintainable software?

The Hexagonal Architecture style cleanly separates between domain logic and outward-facing adapters. This helps us define a clear testing strategy that covers the central domain logic with unit tests
and the adapters with integration tests.

The input and output ports provide very visible mocking points in tests. For each port, we can decide to mock it or to use the real implementation. If the ports are each very small and focused, mocking them is a breeze instead of a chore. The less methods a port interface provides, the less confusion there is about which of the methods we have to mock in a test.



Let's recap how testing architecture elements can help us build 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

Conclusion: Testing Architecture Elements

How does this help me build maintainable software?