Hexagonal Architecture - 편집 역사

2023년 8월 4일 (금) 01:12에 103.159.161.129님의 편집

2023-08-04T01:12:13Z

← 이전 판		2023년 8월 4일 (금) 10:12 판
17번째 줄:		17번째 줄:

	(...) The ultimate benefit of a ports and adapters implementation is '''the ability to run the application in a fully isolated mode.'''</blockquote>		(...) 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

	== 관련 링크 ==		== 관련 링크 ==

2022년 2월 7일 (월) 12:54에 58.149.232.75님의 편집

2022-02-07T12:54:54Z

← 이전 판		2022년 2월 7일 (월) 21:54 판
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 ~~best part~~ of '''~~Hexagonal Architecture~~''' ~~is that it keeps our application flexible for future requirements to come.~~</blockquote>
			(...) The ultimate benefit of a ports and adapters implementation is '''the ability to run the application in a fully isolated mode.'''</blockquote>

	== 관련 링크 ==		== 관련 링크 ==

	* Alistair Cockburn - Hexagonal architecture ([https://alistair.cockburn.us/hexagonal-architecture/ Link])		* 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]])		*위키피디아 페이지 - Hexagonal architecture ([[wikipedia:Hexagonal_architecture_(software)\|Link]])

2022년 2월 7일 (월) 12:13에 Ryanyang님의 편집

2022-02-07T12:13:54Z

← 이전 판		2022년 2월 7일 (월) 21:13 판
15번째 줄:		15번째 줄:
	== 관련 링크 ==		== 관련 링크 ==

	* 위키피디아 페이지 - Hexagonal architecture ([[wikipedia:Hexagonal_architecture_(software)\|Link]])		* Alistair Cockburn - Hexagonal architecture ([https://alistair.cockburn.us/hexagonal-architecture/ Link])
			*위키피디아 페이지 - Hexagonal architecture ([[wikipedia:Hexagonal_architecture_(software)\|Link]])

	[[분류:컴퓨터]]		[[분류:컴퓨터]]

2022년 2월 7일 (월) 12:12에 Ryanyang님의 편집

2022-02-07T12:12:02Z

← 이전 판		2022년 2월 7일 (월) 21:12 판
12번째 줄:		12번째 줄:

	The best part of '''Hexagonal Architecture''' is that it keeps our application flexible for future requirements to come.</blockquote>		The best part of '''Hexagonal Architecture''' is that it keeps our application flexible for future requirements to come.</blockquote>

			== 관련 링크 ==

			* 위키피디아 페이지 - Hexagonal architecture ([[wikipedia:Hexagonal_architecture_(software)\|Link]])

	[[분류:컴퓨터]]		[[분류:컴퓨터]]
	[[분류:IT 전문가]]		[[분류:IT 전문가]]

2022년 2월 7일 (월) 12:07에 Ryanyang님의 편집

2022-02-07T12:07:38Z

← 이전 판		2022년 2월 7일 (월) 21:07 판
5번째 줄:		5번째 줄:

	* 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 / [https://netflixtechblog.com/ready-for-changes-with-hexagonal-architecture-b315ec967749 Link])
			<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.'''


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

Ryanyang: 새 문서: == 정의 == 클린 아키텍처, 육각형 아키텍처, 포트와 어댑터 아키텍처로 번역되는 소프트웨어 아키텍처(설계) 기법. == 관련 포스트 == * Ready for changes with Hexagonal Architecture (Netflix / Mar 11, 2020 / [https://netflixtechblog.com/ready-for-changes-with-hexagonal-architecture-b315ec967749 Link]) 분류:컴퓨터 분류:IT 전문가 분류:IT 분류:Software Architecture 분류:소프트웨어 아키텍처 ...

2022-02-07T11:51:15Z

새 문서: == 정의 == 클린 아키텍처, 육각형 아키텍처, 포트와 어댑터 아키텍처로 번역되는 소프트웨어 아키텍처(설계) 기법. == 관련 포스트 == * Ready for changes with Hexagonal Architecture (Netflix / Mar 11, 2020 / [https://netflixtechblog.com/ready-for-changes-with-hexagonal-architecture-b315ec967749 Link]) 분류:컴퓨터 분류:IT 전문가 분류:IT 분류:Software Architecture 분류:소프트웨어 아키텍처 ...

새 문서

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

== 관련 포스트 ==

* Ready for changes with Hexagonal Architecture (Netflix / Mar 11, 2020 / [https://netflixtechblog.com/ready-for-changes-with-hexagonal-architecture-b315ec967749 Link])

[[분류:컴퓨터]]
[[분류:IT 전문가]]
[[분류:IT]]
[[분류:Software Architecture]]
[[분류:소프트웨어 아키텍처]]
[[분류:설계]]