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

The domain model has no dependencies to incoming and outgoing adapters.

The domain model only has a dependency to outgoing adapters.

The domain model only has a dependency to incoming adapters.

Adapters may not have a dependency to the domain model.

Which of the following is true for a domain-centric architecture?

Which of the following is true for a domain-centric architecture?

Which of the following is not a responsibility of a use case?


Which of the following is not a responsibility of a use case?

Because we don't want to trust all clients to have validated the input correctly

Because invalid input could cause damage to the state of the domain model

Because the validation should be in a central place and not distributed across clients

Why should input be validated in the application layer?

Why should input be validated in the application layer?

Take a quiz to test your understanding of the concepts you learned while implementing a use case.

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: Implementing a Use Case