Cities, organisms, companies, and other systems share the same underlying structure: all rely on a network-based supply of energy to all of its components. The energy can be calories, water, oxygen, electricity, or other supplies that the system cannot function without. Any hiccup in the delivery of the energy can inadvertently lead to demise of the whole system.

Software projects share the same core characteristic. Software also depends on efficient supply of energy. Domain-driven design taught us how to tackle complexity in the heart of software, and I want to discuss how we can tackle complexity in the cardiovascular system of software.

The energy that flows through the cardiovascular system of software is knowledge. You are going to learn how it is spread and delivered to the different components of a software system, the inherent complexity of the process, and how we can optimize the distribution of knowledge to design effective software solutions.