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

A question many project teams I've been part of couldn't answer is how much testing we should do. Is it enough if our tests cover 80% of our lines of code? Should it be higher than that?

## Line coverage

Line coverage is a bad metric to measure test success. Any goal other than 100% is completely [meaningless](https://reflectoring.io/100-percent-test-coverage/) because important parts of the codebase might not be covered at all. And even at 100%, we still can't be sure that every bug has been squashed.


A question many project teams I've been part of couldn't answer is how much testing we should do. Is it enough if our tests cover 80% of our lines of code? Should it be higher than that?

# Line coverage

Line coverage is a bad metric to measure test success. Any goal other than 100% is completely [meaningless](https://reflectoring.io/100-percent-test-coverage/) because important parts of the codebase might not be covered at all. And even at 100%, we still can't be sure that every bug has been squashed.


Learn about how much testing you should implement in your project.

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

How Much Testing is Enough?

Line coverage