Containerization
The packaging of software and its dependencies into isolated, portable execution environments called containers.
Google Anthos in Action
Containerization is the process of packaging an application and its dependencies into containers for portable execution.
- How it is used
- Positions containerization as an optional replatforming step in application modernization, chosen separately for application components.
- How deep it goes
- Outlines suitability criteria and an Anthos Migrate step, but does not specify container build commands or runtime configuration.
- Examples
- Uses a Java application modernization flow and Linux or Windows monoliths to illustrate candidate workloads.
- What you can do after
- Evaluate/understand when to containerize a component with Anthos Migrate and when to retain or migrate it as a VM.
Read how Google Anthos in Action explains containerization →
Rust Servers, Services, and Apps
Containerization packages an application and its dependencies into isolated, portable runtime units called containers.
- How it is used
- Deploys Rust web services and their dependencies consistently across development, production, cloud, and other environments.
- How deep it goes
- Progresses from isolation concepts to a working Dockerfile, image build, container execution, endpoint testing, and image-size concerns.
- Examples
- Uses an Actix Web service, Dockerfile-basic, Docker build and run commands, localhost endpoints, and a 1.32-GB image.
- What you can do after
- Builds and runs a Docker container for a Rust web service, then tests its published HTTP endpoints.
Read how Rust Servers, Services, and Apps explains containerization →
Related concepts
- containerproduces · A software container is an isolated execution environment that packages an application and its dependencies while sharing the host operating system kernel.
- Dockeruses · Docker is a platform and ecosystem for building, distributing, and running applications in containers.
- artifact packagingused by · Artifact packaging is the preparation of a trained model and its associated files and requirements as a deployable unit.
- modernization initiativeused by · A modernization initiative is a planned effort to update existing software, technology, architecture, or organizational capabilities to meet current needs.
- model training serviceuses · A service that provides computation resources and job management for executing model-training code, producing trained models, and tracking training execution.
- dependencyaddresses · A software dependency is a component, resource, or prerequisite on which another software component or operation relies to function or proceed.
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.