liveBook · Manning

Containers as a service

As explained in Developer Experience on Kubernetes

Containerization as a service is an operating model in which a platform team provides application containerization as a managed capability.

Containers as a service is a platform operating model in which a platform team centralizes application containerization and manages the resulting compliance and security responsibilities. It raises the abstraction above Dockerfiles so developers can package applications without mastering every underlying detail. section 3.2.1

The model addresses recurring container-image ownership problems:

  • The platform team maintains the containerization approach and can apply vulnerability patches consistently. section 3.2.1
  • Application developers avoid handling Dockerfile details when those details are not central to their work. section 3.2.1
  • The organization can pursue compliance and security without requiring each development team to maintain its own containerization process. section 3.2.1

How Developer Experience on Kubernetes covers it

How deep it goes
Defines the operating model and its rationale but stops short of specifying an implementation tool or workflow.
Examples
Uses a platform-provided Dockerfile for a new project as the concrete containerization example.
What you can do after
Evaluate when platform-owned containerization can improve developer experience while centralizing compliance and security responsibilities.
How it connects
Links platform teams, application developers, Dockerfiles, container images, compliance, security, and vulnerability patching.

Also explained in

Compare how 4 books explain containers as a service →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Developer Experience on Kubernetes. The section links point to the parts of the book it draws on.