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

Previously, we have discussed how we might implement a use case that modifies the state of our model. How do we go about implementing read-only cases? 



# Implementing read-only case

Let's assume the #key# UI: User Interface #key# needs to display the balance of an account. Do we create a specific use case implementation for this?

It's awkward to talk of use cases for read-only operations like this one. Sure, in the #key# UI: User Interface #key#, the requested data is needed to implement a certain use case that we might call "View Account Balance". If this is considered a use case in the context of the project, by all means we should implement it just like the other ones.



Learn how to tackle a read-only use case.

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

What About Read-Only Use Cases?

Implementing read-only case