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

If the code quality is good, the threshold to add bad code is low.

If the code quality is bad, the threshold to add more bad code is high.

If the code quality is bad, the threshold to add more bad code is low.

If the code quality is high, we automatically only add more good code.

What does the "Broken Windows Theory" mean for code?

What does the “Broken Windows Theory” mean for code?

The use cases will be coupled to each other.

When the code for one use case changes, we'll probably have to change the code for the other use as well.

It's a valid option for use cases that should evolve together.

Which of the following is true about sharing models between use cases?


Which of the following is true about sharing models between use cases?

It couples the domain objects with the use cases, potentially leading to changes in the domain objects that we don't want.

It hides the domain model from the incoming and outgoing adapters.

Which of the following is true about using domain objects as the model in incoming or outgoing ports?

Which of the following is true about using domain objects as the model in incoming or outgoing ports?

It dilutes our architecture, making it somewhat harder to enforce dependencies.

Which of the following is true about skipping incoming ports?

Which of the following is true about skipping incoming ports?

Take a quiz to test your understanding of taking shortcuts consciously.

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: Taking Shortcuts Consciously