Infrastructure resource
An infrastructure resource is an identifiable supporting component or service that provides technical capabilities on which applications or other system components depend.
Platform Engineering on Kubernetes
Application infrastructure is the set of supporting software components and services required by application services, distinct from the underlying infrastructure that runs them.
- How it is used
- Supports application services with databases, message brokers, and other components they need to run.
- How deep it goes
- Works through provisioning and connecting example resources with Helm and Crossplane, while leaving specialist component configuration to operations teams.
- Examples
- Uses PostgreSQL, Redis, and Kafka resources, readiness listings, and Helm values that connect application services to them.
- What you can do after
- Apply it via Crossplane to request infrastructure through Kubernetes resources and connect services using endpoints and Secrets.
Read how Platform Engineering on Kubernetes explains infrastructure resource →
Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform
An infrastructure component is an independently identifiable element of an infrastructure system, such as a server, network, or load balancer.
- How it is used
- Deploys infrastructure resources as composable, testable, and changeable units within infrastructure-as-code systems.
- How deep it goes
- Explains resource composition, provisioning, testing, stateful replacement, and deletion safeguards, but stops short of provider-specific implementation.
- Examples
- Uses servers, networks, routing rules, load balancers, databases, queues, caches, domains, and untagged cloud instances as examples.
- What you can do after
- Operate/configure resources with provisioning tools, preview dependencies, test generated configuration, and remove unused components cautiously.
Building Distributed Applications that Work
An infrastructure resource is a supporting component, such as a database, cache, or message broker, on which an application depends.
- How it is used
- Models supporting components as dependencies coordinated with application services in an Aspire distributed application.
- How deep it goes
- Explains resource modeling and container-versus-integration options; defers security mechanisms and protocols.
- Examples
- Uses an online shop’s database, distributed cache, and message broker, alongside Keycloak and Redis integration examples.
- What you can do after
- Apply it via Aspire AppHost and integrations to connect supporting components, or move existing components while preserving production versions.
Read how Building Distributed Applications that Work explains infrastructure resource →
Related concepts
- factoryproduced by · A factory is a function, method, class, or component that creates and returns objects or other values while encapsulating construction details or selection.
- cloud wasteincludes · Cloud waste is unnecessary consumption of cloud resources or expenditure that does not provide corresponding business or technical value.
- infrastructurecontrasts with · Infrastructure is the foundational physical, digital, and operational resources and systems that support an organization, computing system, or service.
- moduleused 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.
- provisioning toolused by · Software that creates and prepares infrastructure resources and manages their infrastructure-level dependencies.
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.