Robert Smallshire - Domain Driven Design Patterns in Python
Вставка
- Опубліковано 5 вер 2018
- Domain-Driven Design Patterns in Python
[EuroPython 2018 - Talk - 2018-07-27 - Kilsyth]
[Edinburgh, UK]
By Robert Smallshire
Domain-Driven Design (DDD) is an approach to software development that emphasises high-fidelity modelling of the problem domain, and which uses a software implementation of the domain model as a foundation for system design. This approach helps organize and minimize the essential complexity of your software. DDD has been used with success within the traditional enterprise programming ecosystems of Java and .NET, but has seen only limited adoption in the Python community.
In this talk we introduce Python programmers to the core tactical patterns of DDD and show how they can be realised in idiomatic Python, freeing the most valuable parts of your system - the domain model - from onerous dependencies on particular databases or application frameworks.
In this talk we share what we've learned from applying DDD in Python to large projects.
License: This video is licensed under the CC BY-NC-SA 3.0 license: creativecommons.org/licenses/...
Please see our speaker release agreement for details: ep2018.europython.eu/en/speak... - Наука та технологія
This is the BEST explanation of applied DDD from a design standpoint I have ever found.
Great talk! It’s hilariously hard to find such quality content on non-trivial CS topics
Awesome talk on DDD among many others but what makes this one the best one for me is the Python anecdotes.
Amazing video by Robert! One of the best and most practical explanations of DDD in the real world.
Where Can I find a completed demo about DDD?
Great talk. Please don't ever take this video down.
Your slides almost work better as a quick reference than the official one
Thanks!
Aggregates - 25:03
This is an excellent talk and resonates with most of my feelings on the subject especially regarding ORMs. Early in the talk you suggest that event sourcing is perhaps over used, but then later when you talk about domain events you suggest applying those events to the model. From my understanding of the definition this is exactly event sourcing. From what I also understand domain events and events used for event sourcing don’t necessarily have to be the same thing and, in fact, publishing the same events used for event sourcing to other bounded contexts can be detrimental or at least there are trade offs. It might not be a bad idea if you’re doing something like event carried state transfer, but then your contract with those services becomes all of those events so maybe not 🤷🏼♂️ Can you speak to this a bit more?
Fantastic talk and I don't even like Python! (don't hate me, lol). This really helped me to get a grip on DDD concepts!
What do you like?
Does someone know where we can find the slides?
I have the same question
is he 100 foot tall? floating on a moving riser?