|
You are here |
www.paepper.com | ||
| | | | |
www.softdevtube.com
|
|
| | | | | The onion architecture is not as well known as the 3-tier software architecture but is gaining a lot of attention during the microservices era. It structures your software so that it is easy to change technologies without impacting business logic. Coupled with Domain Driven Design (DDD) principles it offers a powerful way to build a | |
| | | | |
blog.gougousis.net
|
|
| | | | | [AI summary] A developer provides a critical re-reading of Domain-Driven Design, contrasting tactical patterns with the strategic importance of domain modeling, ubiquitous language, bounded contexts, domain events, and aggregates. | |
| | | | |
vladikk.com
|
|
| | | | | Let's do a little experiment: try to explain the gist of Domain-Driven Design to someone who has no clue about it. This, especially doing it succinctly, is not easy. Heck, I struggle with it myself. Bounded contexts, entities, domain events, value objects, domains, aggregates, repositories... where do you even start? To find the order in the apparent chaos, I want to analyze the DDD methodology from a rather unusual perspective - by applying Domain-Driven Design to Domain-Driven Design itself. After all, this methodology is intended to deal with complex domains, isn't it? | |
| | | | |
venam.net
|
|
| | | We're used, as software engineers to try to make things perfect, to see things from above, to think we're great architects and creators. What's more important though is to create software that does an important job for someone. What are the best ways to create such software? | ||