Explore >> Select a destination
|
You are here 
|
www.kevindangoor.com | ||
| | | | |
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? | |
| | | | |
www.milanjovanovic.tech
|
|
| | | | | If you were to glance at the folder structure of your system, could you tell what the system is about? Your architecture should communicate what problems it solves. This approach is called sreaming architecture. | |
| | | | |
herbertograca.com
|
|
| | | | | This is a listing of articles about concepts I find essential for any developer to know. This is organized in order of most base structural concepts to most high level concepts and includes good practices, principles, and lists of articles, conference talks and books on software development. This page is in constant enhancement. Good Practices... | |
| | | | |
www.syntasso.io
|
|
| | | Continuous compliance is an essential practice in today's fast-paced software development environment. Platform frameworks like Kratix can help with implementation. | ||
