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

To direct the dependency from the persistence adapter towards the application core

To direct the dependency from the application core towards the persistence adapter

To direct the dependency from the output ports towards the persistence adapter

To direct the dependency from the application services towards the output ports

Why do we apply Dependency Inversion when implementing a persistence adapter?

Why do we apply Dependency Inversion when implementing a persistence adapter?

Mapping the database model into the model used by the output ports

Mapping the model used by the output ports into the database model

Which of the following is not a responsibility of a persistence adapter?

Which of the following is not a responsibility of a persistence adapter?

To avoid dependencies to methods that the client doesn't need

To make the clients depending on the output ports easier testable

To make mocking of the output ports easier to understand

Why might we want to apply the Interface Segregation Principle to slice the output ports?

Why might we want to apply the Interface Segregation Principle to slice the output ports?

Take this quiz to test your understanding of a persistence adapter.

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 Persistence Adapter