Composability
Composability is the property of components or operations that allows them to be combined into larger systems or behaviors through defined interactions.
Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform
Composability is the property of an infrastructure system whose resources can be assembled in different combinations and updated independently.
- How it is used
- Uses modular infrastructure to assemble environments, constrain change impact, and help teams scale through self-service.
- How deep it goes
- Explains independent resource updates, module patterns, repository risks, and assessment questions without detailing implementation syntax.
- Examples
- Uses network, server, load-balancer, database, shared-module, repository, and infrastructure-script examples.
- What you can do after
- Evaluate infrastructure configurations and design modules that combine resources while isolating updates and reducing failure blast radius.
Real-World Cryptography
Composability is the property describing whether a cryptographic primitive retains its intended security when combined with other primitives or protocols.
- How it is used
- Guides decisions about combining cryptographic primitives and protocols without inheriting hidden security failures.
- How deep it goes
- Explains threat-model and composition failures through examples, then points to formal verification rather than proving security manually.
- Examples
- Uses X25519 edge cases, assumed signature uniqueness, communication ambiguity, mini-protocols, and Tamarin modeling.
- What you can do after
- Diagnose/debug protocol compositions by checking assumptions and modeling mini-protocols with Tamarin.
Modern Angular
Composability is the property of software building blocks that allows them to be combined into larger behaviors without being rewritten.
- How it is used
- Improves Angular enterprise applications by making guards, interceptors, directives, services, and configuration easier to reuse and refactor.
- How deep it goes
- Contrasts class- and module-coupled patterns with inject and standalone architecture, but stops short of implementation code.
- Examples
- Uses repeated role or permission checks in HRMS routing guards and interceptors as the central enterprise example.
- What you can do after
- Apply it via Angular's inject function and standalone architecture to reduce duplicated behavior and module coupling.
Related concepts
- infrastructure as codepart of · Infrastructure as code is the practice of defining, provisioning, and managing computing infrastructure through machine-readable code or configuration rather than manual procedures.
- dependency injectionproduced by · Dependency injection is a software design technique in which a component receives its dependencies from outside rather than creating or locating them internally.
- scalabilityproduces · Scalability is the ability of a system, process, or method to accommodate increasing workload, size, or demand while maintaining acceptable operation.
- multi-cloud deploymentpart of · A multi-cloud deployment is an architecture or operating strategy that uses services or infrastructure from two or more cloud providers.
- moduleproduced by · A module is a distinct, bounded software unit that groups related code or functionality and provides an organizational or interaction boundary within a larger system.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.