The Art of Discovering Bounded Contexts by Nick Tune
Вставка
- Опубліковано 8 лип 2024
- Bounded contexts are a cherished member of the microservices family, but they mean lots of different things to lots of different people. So what actually are they? How do you find them? How do you design microservices around them? In this talk you’ll learn about advanced domain-driven design techniques for finding bounded contexts, designing microservices and improving the alignment of your whole organisation.
Instead of naively chopping up a system into arbitrary small pieces and calling them ‘microservices that implement bounded contexts’, or merely thinking cross-functional teams will suffice, deeper, more nuanced design skills are needed. All domains are different- there is no flowchart that guides teams into knowing exactly how to break up a large system into smaller pieces that minimise the costs of handovers and shared dependencies.
Strategic domain-driven design introduced the concept of subdomains; things that change together for business reasons. Accordingly, teams that own things that change together for business reasons will own more decision making and have more autonomy. You will learn how DDD heuristics and Theory of Constraints help you to create maximum autonomy.
Nick Tune is passionate about delighting users, creating business impacts, and crafting quality software, placing an equal focus on improving both the delivery capabilities and alignment of an organisation. He specialises in transformation projects, having worked with a number of organisations in both the public and private sector to achieve continuous delivery. He is the co-author of Patterns, Principles and Practices of Domain-Driven Design, blogs at ntcoding.com, and is currently on a hugely-ambitious adventure with Salesforce where he is a Principal Engineer. - Наука та технологія
Nick Tune is a genius!
Great talk. Thank you for making it a consumable topic for non-engineers. These talks are often focused on helping lead engineers to the water and so they use jargon that others don't understand. This is something I can send anyone.
Ignore the negative comments, this was a practical explanation of bounded contexts Good presentation.
The water thing was probably a good lesson for Nick. The "lack of clarity" criticism is invalid and seems like the person wants to someone else to tell them exactly how to break apart their domain. Most other comments seem good.
Conway's Law. 100% agree that bounded contexts should be optimized for team autonomy and removing bottlenecks to deployment.
One of the most useful talks about software design I've listened so far !
The man if bounded to the glass of water
One of the best talks on bounded contexts.
Good talk. For people who are complaining about the water sipping - I just put a poster note on the left to cover his face - problem solved!
Awesome lessons. Thank you!
one the most sensible talks on DDD, pragmatic!
I really wish we knew why Eric Evans doesn't agree with the primary hypothesis.
Purism. He's the inventor of DDD and holds a pure view on it. Others like Nick have taken his teachings and adapted them to their own experiences. Perfectly natural.
Thanks, really helpful
is there the keynotes of this lesson?
The guy should drink full 3 glasses of water before his next presentation :). Other than that, it was great.
Great talk!
this mush is like a posh chav, I love it
that is a bottomless glass of water
Just what I thought! That slurping sound was so distracting!
Hey Nick, thank you very much for the presentation. Though at the start it felt like you were a little condescending and all that water drinking was distracting, eventually the presentation felt much better. That's my 2 cents, thanks again.
Lovely talk. Drop the water
Nice talk
Talk was awesome.
For people annoyed with the speaker sipping water, I have some questions...
What content are you sharing?
What conferences have you spoken at?
Stop critiquing people that are in the game helping others while you are consistently on the sideline just talking and not contributing value to others.
In other words, show me your conference talk that he should learn from. Then you have the right to criticize.
So the only people who can criticize are those who make content themselves and not the receivers?
@@Orestis125
He's just saying it's easy to criticize - but most people who criticize don't bring anything else to the table.
@@JamesSmith-cm7sg I don't agree to that. Criticism is one of the key terms in improving ones skills, e.g. way of teachings. Then the speaker must be humble enough to learn new perspectives, based on the audience. As a speaker you should speak in a way that makes more sense for all of them then only just some of them. A teachers responsibility is to clarify a complex stuff into manageable and graspable concepts, which I think he is doing just great. And the best improvement of one self if exactly from feedback, whether it is good or bad. But sipping water is to tripping xD (but trivial), and I would also love to have another example. But all over he has done a good job. Thumbs up
@@nugzari939 The point is not about criticizing, but what is critiqued. Zipping water to keep on talking for 45 minutes should be an non factor for the audience. If you can not stand this little annoyance, how can you work in a team with people mumbling while coding, or having allergies or anything. People who criticize water zipping should ask themselves if they are a bit neurotic.
Awesome
One of the most dehydrated talks about software design I've listened so far.
I paused this video to see if I could find any comments about this annoying sipping that kept me from focusing on the merits of the case
Those water sips are so annoying, i could only focus on waiting fpr him to take a sip.
You try to give a talk and have anxiety cause you cotton mouth while you are struggling to speak. Ungrateful man.
Thanks but you could have used a better example..this one was dry not very common app example
19:58 die einzige Sache bei der es um bounded contexte geht.
21:25 DDD = model Hypothesis
40:30
The presenter is a bit annoying, comes off as arrogant, but the content of this talk was very good. I learned some new things, so thank you.
I just can't pay attention to this talk while this guy drinks more water than he speaks
Is that a water fountain never ends
Im trying to cope with your 'water sipping' but EISH... 😥, worst part, im listening to this on the headphones.
People can't talk one hour without sipping water? Are you like 80 years old?
Nice talk, but I needed to stop as the constant water drinking was simply to annoying.
Either you drink water or talk... Please don't do both, it feels rude.
What's with Water sipping?
I am. not sure if I understand your take on bounded context, almost like the ideas were still forming in your brain while you were giving this talk. There was too much back and forth between what was hoped out of listeners.
Also, the idea of going with the flow is not bounded context. Bounded context is what makes sense at a given point in time w.r.t. what needs to be done, not what is going on everywhere else. So, the point of organizational structures and overstepping teams seems like a suggestion where something is being developed where only the dev teams want that thing and not the organization. Such software should not be developed
To me, bounded context is enough "encapsulation" where one entity can independently take decisions (including override) without worrying about other aspects of a system.
And yeah, water drinking is disturbing and not recommended.
I could not take him sipping water every min, was so annoying. Finally had to stop watching this video.
I don't know what is wrong with this guy. Why is he drinking constantly during the presentation? May be he got a lot of alcohol yesterday. Annoying guy.
stupid comment
Stop making noise when drinking water! Its annoying
stop making stupid comments ...