Facade pattern

As explained in Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform

A structural infrastructure design pattern in which a module exposes selected resource attributes as an abstraction for dependent modules.

The facade pattern exposes selected resource attributes through module outputs, giving dependent modules a simplified abstraction instead of direct access to the low-level resource. section 4.3

Storage bucket and access control

A storage-bucket module outputs the bucket name or object. An access-control module consumes that facade to configure permissions. Adding location later can extend the facade without changing the access module. section 4.3

Choose the facade when:

• One low-level module serves a few high-level modules. section 4.6
• You want low implementation and troubleshooting effort while accepting weaker scalability and change isolation. section 4.6
• You need to evolve modules through dependency injection while preserving idempotency and composability. section 4.6

Figure 4.8 The facade simplifies attributes to the name of the storage bucket for use by the access control module.

Shows how the facade reduces a storage bucket's attributes to the name required by an access-control module. section 4.3

How Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform covers it

How deep it goes

Defines the abstraction, demonstrates outputs in code, and compares implementation, troubleshooting, scalability, and isolation trade-offs.

Examples

Uses a GCP storage bucket facade consumed by access-control rules and illustrated with a bucket-name abstraction.

What you can do after

Apply it via module outputs to isolate dependent resources from low-level metadata changes.

How it connects

Connects dependency injection with dependency inversion, inversion of control, adapter pattern, and mediator pattern.

liveBookmanning.com

Read Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  Software Design for Python ProgrammersThe Façade pattern is a reusable design model that provides a simplified interface to a complex subsystem.
• 

  liveBookmanning.com
  Object-Oriented Software Design in C++The Façade Design Pattern is a structural design pattern that provides a unified, simplified interface to a set of subsystem interfaces.

Compare how 3 books explain facade pattern →

Related concepts

• design patternkind of · A design pattern is a reusable, general solution structure for a recurring software design problem in a particular context.
• architectural subsystemuses · An architectural subsystem is a distinct, cohesive part of a larger system that provides related functionality through interacting components and defined boundaries.
• dependency injectionuses · Dependency injection is a software design technique in which a component receives its dependencies from outside rather than creating or locating them internally.
• contractproduces · An API contract is a specification of the operations, data, and behavioral expectations that govern interactions between software components.
• natural language interfaceproduces · A natural language interface enables interaction with a system through human-language text or speech.

This explainer was generated by Manning's knowledge graph from the text of Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform. The section links point to the parts of the book it draws on.