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

# Persistence adapter

This is what a persistence adapter usually does:

1. Takes input 
2. Maps input into database format
3. Sends input to the database
4. Maps database output into application format
5. Returns output



## Take input

The persistence adapter takes input through a port interface. The input model may be a domain entity or an object dedicated to a specific database operation, as specified by the interface.

## Map input into database format, and send input to the database

It then maps the input model to a format it can work with to modify or query the database. In Java projects, we commonly use the #key# JPA: Java Persistence API #key#
 to talk to a database, so we might map the input into #key# JPA: Java Persistence API #key# entity objects that reflect the structure of the database tables. Depending on the context, mapping the input model into #key# JPA: Java Persistence API #key# entities may be a lot of work for little gain, so we'll talk about strategies that do not involve mapping in the chapter ["Mapping Between Boundaries"](https://www.educative.io/courses/hexagonal-architecture-web-apps/the-no-mapping-strategy).



Learn what a persistence adapter is and its responsibilities.


Responsibilities of a Persistence Adapter

Learn what a persistence adapter is and its responsibilities.

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

Responsibilities of a Persistence Adapter

Persistence adapter

Take input