liveBook · Manning

Boundary keeper

As explained in Grokking Software Architecture

A Boundary Keeper is an architectural role responsible for preserving component boundaries and preventing responsibilities from leaking across them.

A Boundary Keeper helps a team keep responsibilities in their proper places. Think friendly traffic cop, not codebase dictator: guide teams to own their boundaries and make the long-term cost of logic leaks clear. Keeping business logic out of UI code and preventing database queries from taking over the system makes changes less likely to break unrelated areas and supports maintainability and testability. section 2.3

Watch for responsibilities crossing boundaries:

  • Business logic leaking into UI code, or database queries taking over the system. section 2.3
  • A raw HTTP call inside business logic lets the outside world reach the core domain directly. A Service Layer can act as a protective wall instead. section 10.4.1

How Grokking Software Architecture covers it

How deep it goes
Defines the role, names common logic leaks, and illustrates a Service Layer boundary with a production failure.
Examples
Uses business logic in UI code, sprawling database queries, and a raw HTTP call inside a checkout workflow.
What you can do after
Diagnose boundary leaks and recognize when a Service Layer should protect core business logic from an external call.
How it connects
Connects Separation of Concerns with business logic, UI code, database queries, and the Service Layer.

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.