Protocol

Hide volatile decisions behind stable interfaces

Information hiding protects the rest of the system from volatility.

About 1 min read

Before you use it

Use when
  • When callers depend directly on internal details that change often.

Keep this limit in mind

  • Modularity trades coordination inside a boundary for coordination across interfaces. Do not split systems simply to make diagrams or org charts look cleaner.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

Why it matters

Define an interface around the capability and keep likely-to-change representation or rules inside. Expose only what consumers need for stable use.

Steps

  1. Name the volatile design decision.
  2. Define what consumers actually need.
  3. Create a stable contract around that need.
  4. Test whether internal change can occur without caller changes.

An example

Downstream consumers request a canonical customer status rather than reading several internal tables whose representation may change.

Check your result

A representative internal change can be made without coordinated edits to every consumer.

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingHide volatile decisions behind stable interfaces

Evidence and sources
Supports

Parnas showed that modularization outcomes depend on decomposition criteria and argued for boundaries that hide changeable design decisions to improve flexibility and comprehensibility.

This is foundational software-design reasoning; organizational adaptations require separate validation.

On the Criteria To Be Used in Decomposing Systems into Modules · Abstract and design comparison

All sources (1)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details