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 adapters use the application core's model.

The application core uses the adapter's models.

The application core and the adapters all use the persistence adapter's model.

What is true for a "No-Mapping-Strategy"?

What is true for a “No-Mapping-Strategy”?

The adapters and application core share the same model.

The application core maps into the models of the adapters.

The adapters map into the model of the application core.

Only outgoing adapters have their own model.

Which of the following is true for a "Two-Way Mapping-Strategy"?

Which of the following is true for a “Two-Way Mapping-Strategy”?

The application core provides a separate model for each use case.

The use case models are different from the domain model.

Which of these is true for a "Full" mapping strategy?

Which of these is true for a “Full” mapping strategy?

Take a quiz to test your understanding of the concepts you learned in this chapter.


Quiz: Mapping Between Boundaries

Take a quiz to test your understanding of the concepts you learned in this chapter.

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: Mapping Between Boundaries