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

We start by looking at a domain entity at the center of our architecture. Let's recall the `Account` entity from the chapter ["Implementing a Use Case"](https://www.educative.io/courses/hexagonal-architecture-web-apps/implementing-the-domain-model). The state of an `Account` consists of a balance the account had at a certain point in the past (the baseline balance) and a list of deposits and withdrawals (activities) since then.
## Account test
We now want to ensure that the `withdraw()` method works as expected:


We start by looking at a domain entity at the center of our architecture. Let's recall the `Account` entity from the chapter ["Implementing a Use Case"](https://www.educative.io/courses/hexagonal-architecture-web-apps/implementing-the-domain-model). The state of an `Account` consists of a balance the account had at a certain point in the past (the baseline balance) and a list of deposits and withdrawals (activities) since then.
# Account test
We now want to ensure that the `withdraw()` method works as expected:


Learn how to test an entity with 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 Domain Entity with Unit Tests

Account test