liveBook · Manning

Data flow

As explained in Grokking Software Architecture

Data flow is the movement of information between software layers or components, potentially in multiple directions.

In a layered system, commands travel downward, but data can travel both ways: input moves down, and results return up. A lower layer may return data without knowing which higher layer receives it. section 4.2.1

Keep the two kinds of flow distinct:

  • Commands carry control downward; dependencies point in that same direction. section 4.6.1
  • Data travels both down and up, but lower layers return results rather than initiating commands upward. section 4.6.1

An order passes through layers

The Presentation layer sends input for “Save Order” downward; lower layers process it and return result data upward. section 4.6.1

How Grokking Software Architecture covers it

How deep it goes
Explains flow directions through layered examples and a blueprint, without providing code-level implementation.
Examples
Uses order retrieval and saving to illustrate commands moving down and results returning up.
What you can do after
Understand how data can return across layers without reversing command or dependency direction.
How it connects
Connects data flow with command flow, dependencies, and separation of concerns.

Also explained in

Compare how 4 books explain data flow →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Software Architecture. The section links point to the parts of the book it draws on.