행위

"Hexagonal Architecture"의 두 판 사이의 차이

라이언의 꿀팁백과

 
(사용자 2명의 중간 판 3개는 보이지 않습니다)
3번째 줄: 3번째 줄:


== 관련 포스트 ==
== 관련 포스트 ==
클린 아키텍처 관련 글에서 인상 깊었던 내용을 작성함


* Ready for changes with Hexagonal Architecture (Netflix / Mar 11, 2020 / [https://netflixtechblog.com/ready-for-changes-with-hexagonal-architecture-b315ec967749 Link])
==== Ready for changes with Hexagonal Architecture (Netflix, Mar 11, 2020) ====
<blockquote>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.'''
<blockquote>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.'''
(...) 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.</blockquote>
==== Hexagonal architecture (Alistair Cockburn, 2008) ====
<blockquote>One of the great bugaboos of software applications over the years has been infiltration of business logic into the user interface code.
(...) The ultimate benefit of a ports and adapters implementation is '''the ability to run the application in a fully isolated mode.'''</blockquote>
Layered Architecture, Clean Architecture, Hexagonal Architecture 한글 설명 포스트
https://gngsn.tistory.com/258
Clean Architecture 관련 도서


https://github.com/thombergs/buckpal
== 관련 링크 ==
* Alistair Cockburn - Hexagonal architecture ([https://alistair.cockburn.us/hexagonal-architecture/ Link])
* Ready for changes with Hexagonal Architecture (Netflix / Mar 11, 2020 / [https://netflixtechblog.com/ready-for-changes-with-hexagonal-architecture-b315ec967749 Link])
*위키피디아 페이지 - Hexagonal architecture ([[wikipedia:Hexagonal_architecture_(software)|Link]])


The best part of '''Hexagonal Architecture''' is that it keeps our application flexible for future requirements to come.</blockquote>
[[분류:컴퓨터]]
[[분류:컴퓨터]]
[[분류:IT 전문가]]
[[분류:IT 전문가]]

2023년 8월 4일 (금) 10:12 기준 최신판

1 정의[편집 | 원본 편집]

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

2 관련 포스트[편집 | 원본 편집]

클린 아키텍처 관련 글에서 인상 깊었던 내용을 작성함

2.1 Ready for changes with Hexagonal Architecture (Netflix, Mar 11, 2020)[편집 | 원본 편집]

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.

2.2 Hexagonal architecture (Alistair Cockburn, 2008)[편집 | 원본 편집]

One of the great bugaboos of software applications over the years has been infiltration of business logic into the user interface code.


(...) The ultimate benefit of a ports and adapters implementation is the ability to run the application in a fully isolated mode.


Layered Architecture, Clean Architecture, Hexagonal Architecture 한글 설명 포스트

https://gngsn.tistory.com/258


Clean Architecture 관련 도서

https://github.com/thombergs/buckpal

3 관련 링크[편집 | 원본 편집]

  • Alistair Cockburn - Hexagonal architecture (Link)
  • Ready for changes with Hexagonal Architecture (Netflix / Mar 11, 2020 / Link)
  • 위키피디아 페이지 - Hexagonal architecture (Link)