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

Which of the following is/are the “responsibility” of a software component?

Which of the following is/are the “responsibility” of a software component?

The web layer code no longer depends on the domain code.

The persistence code no longer depends on the domain code.

The web layer code no longer depends on the persistence code.

The domain code no longer depends on the persistence code.

What do we gain by inverting dependencies?

What do we gain by inverting dependencies?

The domain code does not depend on code from any other layer of the architecture.

What is the main feature of a domain-centric architecture like "Clean Architecture" or "Hexagonal Architecture"?

What is the main feature of a domain-centric architecture like “Clean Architecture” or “Hexagonal Architecture”?

Take a quiz to test your understanding of inverting dependencies.

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: Inverting Dependencies