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

The next architecture element to test is the use cases. Let's look at a test of the `SendMoneyService` discussed in the chapter ["Implementing a Use Case"](https://www.educative.io/courses/hexagonal-architecture-web-apps/implementing-the-domain-model).
The "Send Money" use case locks the source `Account` so no other transaction can
change its balance in the meantime. If we can successfully withdraw the money from the source account, we lock the target account as well and deposit the money there. Finally, we unlock both accounts again.

## Send money service test

We want to make sure that everything works as expected when the transaction succeeds:

The next architecture element to test is the use cases. Let's look at a test of the `SendMoneyService` discussed in the chapter ["Implementing a Use Case"](https://www.educative.io/courses/hexagonal-architecture-web-apps/implementing-the-domain-model).
The "Send Money" use case locks the source `Account` so no other transaction can
change its balance in the meantime. If we can successfully withdraw the money from the source account, we lock the target account as well and deposit the money there. Finally, we unlock both accounts again.

# Send money service test

We want to make sure that everything works as expected when the transaction succeeds:

Learn how to test use cases with the help of unit tests.

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

Testing a Use Case with Unit Tests

Send money service test