Domain-Driven Design & Event Storming, with Jakub Pilimon

December 5, 2018 Michael Coté

Flexible software usually means well modularized software. Instead of one big ball of code, you want to create components that work together. Dividing up your application into those components has always been a bugbear of design and it's what domain-driven design (DDD) is trying to solve. In this episode, Coté talks with Jakub Pilimon to figure out what DDD is, plus how event storming is used to find domains. Also, outside of Poland, is it "evangelist" or "advocate"?

Subscribe, follow, feedback

Feedback: podcast@pivotal.io.

About the Author

Michael Coté

Michael Coté works on the advocates team for VMware Tanzu. See @cote for more.

More Content by Michael Coté
Previous
Episode 104: Improving Healthcare Data Interoperability with Cerner’s Greg Meyer
Episode 104: Improving Healthcare Data Interoperability with Cerner’s Greg Meyer

In this week's episode of Pivotal Conversations, Dormain and Jeff chat with Greg Meyer, a distinguished eng...

Next
Episode 103: Domain-Driven Design & Event Storming, with Jakub Pilimon
Episode 103: Domain-Driven Design & Event Storming, with Jakub Pilimon

Flexible software usually means well modularized software. Instead of one big ball of code, you want to cre...