liveBook · Manning

Physical separation

As explained in Grokking Software Architecture

Physical separation deploys application parts onto different machines or processes that communicate across execution boundaries.

Physical separation places application parts on different machines or processes that communicate over a network. Think of separate buildings: a web server, an application server, and a database server. This describes deployment, not how code is organized. section 4.2.3

Figure 4.2 Layers are a logical separation, while tiers are a physical separation.

See how logical layers differ from physical tiers. section 4.2.3

Keep these distinctions clear:

  • Layers organize code by responsibility; tiers describe where parts are deployed. section 4.2.3
  • A three-layer application can run on one server or across three tiers. section 4.2.3
  • Running the presentation layer on ten servers for traffic is horizontal scaling, not ten tiers. A new tier crosses a network boundary to a different responsibility. section 4.2.3

When separation is only physical

Five services that share one database remain tightly coupled: a schema change can break them all. If one service also depends on a live synchronous call to another, the caller can fail when the other service crashes. The result is a distributed monolith: network complexity without the agility of genuine decoupling. section 12.2.4

How Grokking Software Architecture covers it

How deep it goes
Defines tiers, contrasts them with layers, and warns that horizontal scaling alone does not create a tier.
Examples
Uses web, application, and database servers as separate buildings, and contrasts scaling one presentation tier across ten servers.
What you can do after
Evaluate whether deployment creates a new tier by checking for a network boundary to a different responsibility.
How it connects
Connects physical separation to logical layers, network boundaries, microservices, shared databases, and synchronous coupling.

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.