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

## Returning data

Once the use case has done its work, what should it return to the caller? 

Similar to the input, it has benefits if the output is as specific to the use case as possible. The output should only include the data that is really needed for the caller to work. 

In the code example of the "Send Money" use case above, we return a `boolean`. This is the minimal and most specific value we could possibly return in this context.

## Returning entire object

We might be tempted to return a complete `Account` with the updated entity to the caller. Perhaps the caller is interested in the new balance of the account? 



# Returning data

Once the use case has done its work, what should it return to the caller? 

Similar to the input, it has benefits if the output is as specific to the use case as possible. The output should only include the data that is really needed for the caller to work. 

In the code example of the "Send Money" use case above, we return a `boolean`. This is the minimal and most specific value we could possibly return in this context.

# Returning entire object

We might be tempted to return a complete `Account` with the updated entity to the caller. Perhaps the caller is interested in the new balance of the account? 



Learn about different output models for different use cases and how they can help in writing maintainable code.

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

Different Output Models for Different Use Cases

Returning data

Returning entire object