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?

Incoming and outgoing ports act as gatekeepers between the layers of our application and define how the layers communicate with each other and also decide if and how we map between layers.

With narrow ports in place for each use case, we can choose different mapping strategies for different use cases and even evolve them over time without affecting other use cases, thus selecting the best strategy for a certain situation at a certain time.


# How does this help me build maintainable software?

Incoming and outgoing ports act as gatekeepers between the layers of our application and define how the layers communicate with each other and also decide if and how we map between layers.

With narrow ports in place for each use case, we can choose different mapping strategies for different use cases and even evolve them over time without affecting other use cases, thus selecting the best strategy for a certain situation at a certain time.


Let's recap mapping between boundaries and how it can help 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: Mapping Between Boundaries

How does this help me build maintainable software?