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?
When building a web adapter for an application, we should keep in mind that we're building an adapter that translates #key# HTTP: Hypertext Transfer Protocol #key# method calls to use cases of our application and translates the results back to #key# HTTP: Hypertext Transfer Protocol #key#, and does not do any domain logic.

The application layer, on the other hand, should not do #key# HTTP: Hypertext Transfer Protocol #key#, so we should make sure to not leak #key# HTTP: Hypertext Transfer Protocol #key# details. This makes the web adapter replaceable by another adapter should the need arise. 


# How does this help me build maintainable software?
When building a web adapter for an application, we should keep in mind that we're building an adapter that translates #key# HTTP: Hypertext Transfer Protocol #key# method calls to use cases of our application and translates the results back to #key# HTTP: Hypertext Transfer Protocol #key#, and does not do any domain logic.

The application layer, on the other hand, should not do #key# HTTP: Hypertext Transfer Protocol #key#, so we should make sure to not leak #key# HTTP: Hypertext Transfer Protocol #key# details. This makes the web adapter replaceable by another adapter should the need arise. 


Let's recap the importance of a web adapter and how it can help in writing maintainable software. 

Conclusion: Implementing a Web Adapter

Let's recap the importance of a web adapter and how it can help in writing 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: Implementing a Web Adapter

How does this help me build maintainable software?