행위

Hexagonal Architecture

라이언의 꿀팁백과

Ryanyang (토론 | 기여)님의 2022년 2월 7일 (월) 21:13 판

1 정의

클린 아키텍처, 육각형 아키텍처, 포트와 어댑터 아키텍처로 번역되는 소프트웨어 아키텍처(설계) 기법.

2 관련 포스트

  • Ready for changes with Hexagonal Architecture (Netflix / Mar 11, 2020 / Link)

The idea of Hexagonal Architecture is to put inputs and outputs at the edges of our design. Business logic should not depend on whether we expose a REST or a GraphQL API, and it should not depend on where we get data from - a database, a microservice API exposed via gRPC or REST, or just a simple CSV file. The pattern allows us to isolate the core logic of our application from outside concerns. Having our core logic isolated means we can easily change data source details without a significant impact or major code rewrites to the the codebase.


(...) We knew that a prerequisite to great development velocity was to have a test suite that is reliable and super fast. We don't think of it as a nice to have, but a must-have.


The best part of Hexagonal Architecture is that it keeps our application flexible for future requirements to come.

3 관련 링크

  • Alistair Cockburn - Hexagonal architecture (Link)
  • 위키피디아 페이지 - Hexagonal architecture (Link)