DEV Community

# hexagonal

Posts

👋 Sign in for the ability to sort posts by relevant, latest, or top.
Retries and Circuit Breakers Belong in the Adapter, Not Your Use Case

Retries and Circuit Breakers Belong in the Adapter, Not Your Use Case

Comments
6 min read
A Domain Logger Port: Decoupling From PSR-3 Without Losing Context

A Domain Logger Port: Decoupling From PSR-3 Without Losing Context

Comments
7 min read
Translate Infrastructure Errors at the Adapter, Not in Your Domain

Translate Infrastructure Errors at the Adapter, Not in Your Domain

Comments
6 min read
Your Repository Isn't a Repository, It's a DAO

Your Repository Isn't a Repository, It's a DAO

Comments
9 min read
Domain Model vs Persistence Model: The Mapper Layer in Go

Domain Model vs Persistence Model: The Mapper Layer in Go

Comments
8 min read
Application Service vs Domain Service in Go: Two Layers, Different Jobs

Application Service vs Domain Service in Go: Two Layers, Different Jobs

Comments
8 min read
Functional Core, Imperative Shell in Go: Where Side Effects Belong

Functional Core, Imperative Shell in Go: Where Side Effects Belong

Comments
8 min read
The Anti-Corruption Layer for a Legacy Database You Cannot Replace

The Anti-Corruption Layer for a Legacy Database You Cannot Replace

Comments
8 min read
Errors as Domain Concepts: Typed Errors That Carry Meaning in Go

Errors as Domain Concepts: Typed Errors That Carry Meaning in Go

Comments
7 min read
Hexagonal for the Rest of Us: Ports and Adapters Without DDD

Hexagonal for the Rest of Us: Ports and Adapters Without DDD

Comments
8 min read
Symfony Is Also an Adapter (Yes, Even With All Its Glue)

Symfony Is Also an Adapter (Yes, Even With All Its Glue)

2
Comments
9 min read
Hexagonal architecture + PON: Ports & Adapters to decouple the engine

Hexagonal architecture + PON: Ports & Adapters to decouple the engine

4
Comments
5 min read
👋 Sign in for the ability to sort posts by relevant, latest, or top.