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

Because the domain code is usually simpler than the persistence code

Because we want to get feedback on whether we're building the right solution to a domain problem before writing persistence code

Because the persistence code can be auto-generated

We don't. We usually want to write the persistence code first because it's the foundation of an application.

Why might we want to write domain code before we write persistence code?

Why might we want to write domain code before we write persistence code?

Because the domain code may access the database code, leading to many and potentially unwanted dependencies

Because we will probably have to deal with persistence issues in the domain layer

Because the entities used for database mapping are often used in the domain layer

Why does a layered architecture often lead to strong coupling between the domain layer and the database layer?

Why does a layered architecture often lead to strong coupling between the domain layer and the database layer?

A broad service supports too many use cases and makes it hard to find the use cases in the code.

A broad service has too many lines of code.

A broad service is likely to leak abstractions into the other architecture layers.

What is the main problem with "broad services"?

What is the main problem with “broad services”?

Take a quiz to test your understanding of the drawbacks of layers in software architecture.

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: What's Wrong with Layers?