hexagonal-architecture

Ports and adapters / hexagonal architecture - clarification of terms and implementation

由 ￡可爱￡侵袭症＋ 提交于 2020-12-27 07:44:44
问题 After reading different sources about the Ports & Adapters architecture including Alistair Cockburn's original article I am still not sure about the definite meaning of the terms "port" and "adapter" - especially when it comes to mapping these concepts to implementation artifacts. Several sources (e. g. this post) imply that the ports in this architecture pattern are artifacts at the very outside, followed by the adapters in the intermediate layer that translate between the ports and the

Ports and adapters / hexagonal architecture - clarification of terms and implementation

由 生来就可爱ヽ(ⅴ＜●) 提交于 2020-12-27 07:42:31
问题 After reading different sources about the Ports & Adapters architecture including Alistair Cockburn's original article I am still not sure about the definite meaning of the terms "port" and "adapter" - especially when it comes to mapping these concepts to implementation artifacts. Several sources (e. g. this post) imply that the ports in this architecture pattern are artifacts at the very outside, followed by the adapters in the intermediate layer that translate between the ports and the

Ports and adapters / hexagonal architecture - clarification of terms and implementation

由 坚强是说给别人听的谎言 提交于 2020-12-27 07:41:37
问题 After reading different sources about the Ports & Adapters architecture including Alistair Cockburn's original article I am still not sure about the definite meaning of the terms "port" and "adapter" - especially when it comes to mapping these concepts to implementation artifacts. Several sources (e. g. this post) imply that the ports in this architecture pattern are artifacts at the very outside, followed by the adapters in the intermediate layer that translate between the ports and the

In an Onion type architecture, should the entities cross the outer layer?

由 假如想象 提交于 2019-12-10 11:43:17
问题 I've been trying to understand this new kind of architecture which names can be Onion architecture, Clean architecture, Ports and Adapters, etc. If I take the abstraction of Ports and Adapters, when I adapt my application for a particular port, is it ok for me to give the port an entity from inside my application? Or am I always supposed to adapt the entities also, to fit the port? Example: Say I have a Customer entity. I have a UI that uses my application. My UI calls through an Adapter to

Should my Domain Exceptions be thrown from Application Layer?

由 依然范特西╮ 提交于 2019-12-09 06:25:12
问题 I'm reading Vaughn Vernon Book - Implementing Domain Driven Design. There is an example of a Project Management Application. There are aggregates like BacklogItem, Sprint, etc. If I have BacklogItemNotFoundException defined in Domain layer. Should my Rest adapter catch it and transform into NotFoundHttpResult? Or any other broken invariant exceptions like: EmailPatternBrokenException or TooManyCharactersForNameException or whatever should be handled in Rest adapter(ports&adapters architecture

Rails: How do I make my rails project a Hexagonal rails project?

由 两盒软妹~` 提交于 2019-12-05 02:55:39
问题 I attended a meetup yesterday on scaling Rails, and one topic was Hexagonal Rails. However, I've only been doing Rails for a year, and am really comfortable (maybe too comfortable) with the MVC structure, so I don't really understand what adapter and message queue are. Here's an article about it: http://victorsavkin.com/post/42542190528/hexagonal-architecture-for-rails-developers And a pic: http://blog.mattwynne.net/wp-content/uploads/2012/06/hexagonal_architecture_sketch.jpg To my

Onion architecture compared to hexagonal

由 独自空忆成欢 提交于 2019-12-04 10:12:43
问题 Is there any difference between them (onion | hexagonal), from my understanding they are just the same, they focus upon the domain which is at the core of the application and should be technology / framework agnostic. What are the differences between them if any ? Also I see no real advantage on using one over the other or even against an N-layered architecture, if done bad just following any of them won't make any difference What are the benefits of using one over the other and why you would

Rails: How do I make my rails project a Hexagonal rails project?

由 倾然丶 夕夏残阳落幕 提交于 2019-12-03 19:03:16
I attended a meetup yesterday on scaling Rails, and one topic was Hexagonal Rails. However, I've only been doing Rails for a year, and am really comfortable (maybe too comfortable) with the MVC structure, so I don't really understand what adapter and message queue are. Here's an article about it: http://victorsavkin.com/post/42542190528/hexagonal-architecture-for-rails-developers And a pic: http://blog.mattwynne.net/wp-content/uploads/2012/06/hexagonal_architecture_sketch.jpg To my understanding, I think it's about decoupling the parts so that actions are specifically filtered and passed to

Onion architecture compared to hexagonal

由 人走茶凉 提交于 2019-12-03 05:31:56
Is there any difference between them (onion | hexagonal), from my understanding they are just the same, they focus upon the domain which is at the core of the application and should be technology / framework agnostic. What are the differences between them if any ? Also I see no real advantage on using one over the other or even against an N-layered architecture, if done bad just following any of them won't make any difference What are the benefits of using one over the other and why you would use it ? when to use it? Thanks choquero70 What are the differences between them if any? Onion: There
订阅 hexagonal-architecture