DDD would be a good addition to that list. Domain Driven Design made functional would be my recommendation for those wanting to look into it.
Software Architecture Patterns: 5 minute read
11–20 of 73 posts
Re: Software Architecture Patterns: 5 minute read
#12I don't think the term "Microkernel Architecture" should be used in this context. I think "Modular Architecture," (or Plug-in like is mentioned) gets closer to this extension-based pattern.
The reason being that there's no relevance to the kernel, and modular kernels, also take this approach with replaceable plug-ins or extensions.
Re: Software Architecture Patterns: 5 minute read
#13I tend to design architectures that combine facets of all of these.
Re: Software Architecture Patterns: 5 minute read
#14DDD would be a good addition to that list. Domain Driven Design made functional would be my recommendation for those wanting to look into it.
DDD is completely orthogonal to software architecture.
Re: Software Architecture Patterns: 5 minute read
#15I tend to design architectures that combine facets of all of these.
Probably everybody does. Purists usually don’t get very far when they face the real world.
Re: Software Architecture Patterns: 5 minute read
#16I don't think the term "Microkernel Architecture" should be used in this context. I think "Modular Architecture," (or Plug-in like is mentioned) gets closer to this extension-based pattern. The reason being that there's no relevance to the kernel, and modular kernels, also take this approach with replaceable plug-ins or extensions.
I think people gravitate to it because "kernel" feels like a cool word and some people have heard of OS microkernels being modular. As you say, "modular architecture" is a much clearer way to express the intent and conveys the purpose without being pretentious.
Re: Software Architecture Patterns: 5 minute read
#17I tend to design architectures that combine facets of all of these.
That's what I was thinking as I looked at the list. It a nice little overview, perhaps for starting a discussion, but it doesn't capture how you'd use them in practice. When presented separately they appear like they should be applied in a standalone fashion.
Re: Software Architecture Patterns: 5 minute read
#18Re: Software Architecture Patterns: 5 minute read
#19I tend to design architectures that combine facets of all of these.
Probably everybody does. Purists usually don’t get very far when they face the real world.
> Purists usually don’t get very far when they face the real world.
This is true. I said as much to someone else, in another thread: https://news.ycombinator.com/item?id=29021254
Re: Software Architecture Patterns: 5 minute read
#20What I nerver understood:
* How to disconnect the domain model from persistence.
Some solutions add the OR Annotations to the domain model. Some other map the domain model to persistence with a Mapper-layer.
But all of them have some constraints. For e.g. on a web api I receive a dto, map it to a domain model, map it to a persistence model and vice versa. Not much gained imho. In this example I would add the OR-annotations to the domain model and configure many-to-many by "text" so that they are not contained in the domain model.
What are your thoughts?