The Art of Discovering Bounded Contexts by Nick Tune

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.

[ryananderson]

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.

[alejandrourizar]

Ignore the negative comments, this was a practical explanation of bounded contexts Good presentation.

[brainoverflow]

One of the most useful talks about software design I've listened so far !

[maxigutierrez]

The man if bounded to the glass of water

[sudonick]

One of the best talks on bounded contexts.

[marissamayfield]

Conway's Law. 100% agree that bounded contexts should be optimized for team autonomy and removing bottlenecks to deployment.

[onlyitj]

one the most sensible talks on DDD, pragmatic!

[rostyslavv]

I am curious, is it single malt 20-years water, or what?

[methodsignature]

I really wish we knew why Eric Evans doesn't agree with the primary hypothesis.

[nairooznilafdeen]

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!

[Bizmonger]

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.

[metehanmutlu]

One of the most dehydrated talks about software design I've listened so far.

[TricoliciSerghei]

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.

[Droubek]

The guy should drink full 3 glasses of water before his next presentation :). Other than that, it was great.

[cupofkoa]

this mush is like a posh chav, I love it

[marcm]

19:58 die einzige Sache bei der es um bounded contexte geht.
21:25 DDD = model Hypothesis
40:30

[kennethcarvalho]

Thanks but you could have used a better example..this one was dry not very common app example

[JamesSmith-cmsg]

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.

[SkyaTura]

I just can't pay attention to this talk while this guy drinks more water than he speaks

[rostyslavv]

Someday people will realize, that drinking water with microphone near mouth - its bad idea