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

Why do we want high coverage with unit tests?

Why do we want high coverage with unit tests?

Integration tests because they can test if the business logic works in combination with the database

Unit tests because they can test our business logic in isolation

System tests because they can test if the business logic works end-to-end

All things being equal, what is the best test type for testing the business logic in domain entities and use cases?

All things being equal, what is the best test type for testing the business logic in domain entities and use cases?

Unit tests because they can test the adapter logic in isolation

Integration tests because they also cover the mapping between incoming and outgoing models and our central domain logic

System tests because they can test if the adapters work end-to-end

All things being equal, what is the best test type for testing the logic of our incoming and outgoing adapters?

All things being equal, what is the best test type for testing the logic of our incoming and outgoing adapters?

Take a quiz to test your understanding of testing architectural elements.

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: Testing Architecture Elements