Containerization

As explained in Google Anthos in Action

Containerization is the process of packaging an application and its dependencies into containers for portable execution.

Containerization is one route for modernizing an application, not a requirement for every workload. A modern application may already be containerized, integrated with CI/CD, and running on Anthos. A traditional Linux or Windows monolith may instead be a candidate for containerization with M4A. Once on Anthos, an application can be refactored further toward microservices; containerizing it does not itself complete that refactoring. section 15.3.4

Choose the deployment path component by component:

• Identify the application or component, assess whether it is suitable, and use Anthos Migrate to containerize suitable targets. section 16.2.1
• Consider a GCE VM first for a business-critical application when adopting new operational patterns would add too much risk. Teams can learn Kubernetes and Anthos with less critical workloads before revisiting it. section 16.2.1
• Keep a component on a VM when licensing, support readiness, compliance, interactions with other applications, or hardware investments make containerization unsuitable. Applications needing particular drivers or legacy support may also be migrated directly as VMs and refactored later. section 16.2.1 section 15.3.4

Figure 16.2 Modernizing a Java application

The high-level Java modernization flow illustrates where the suitability decision and containerization step fit in a broader application plan. section 16.2.1

How Google Anthos in Action covers it

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 it assumes

Recognizes that teams may need to learn Kubernetes, Anthos, and the containerized-application tool chain before moving critical 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.

How it connects

Links containerization to CI/CD, Anthos, virtual machines, Kubernetes, and later microservice refactoring.

liveBookmanning.com

Read Google Anthos in Action on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  Rust Servers, Services, and AppsContainerization packages an application and its dependencies into isolated, portable runtime units called containers.

Compare how 2 books explain 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.

This explainer was generated by Manning's knowledge graph from the text of Google Anthos in Action. The section links point to the parts of the book it draws on.