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 web adapter shouldn't know about the domain model

Because it's easier to identify the parts of the code that are exposed to the web

Because the web adapter is not to be trusted

Because the web adapter and application layer might be built by different people

Why should the web adapter only communicate with the application via input ports?

<p>Why should the web adapter only communicate with the application via input ports?</p>


Mapping the web model into the input model of the use cases

Mapping the output model of the use case into an HTTP response

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


<p>Which of the following is not a responsibility of a web adapter?</p>


Take a quiz to test your understanding of web adapters.

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