liveBook · Manning

Managed service

A managed service is a technology service for which an external provider handles specified operational responsibilities, such as managing its software or infrastructure.

How 3 Manning books explain it

Kafka for Architects

A managed service is a provider-operated offering in which the provider administers the underlying software and infrastructure for the customer.

How it is used
Simplifies Kafka deployment and operations by transferring infrastructure administration to a cloud provider.
How deep it goes
Explains operational benefits and control trade-offs, but stops short of provider-specific setup or complete operational procedures.
Examples
Uses Customer 360 topic configuration and cloud services such as Amazon Kinesis, Google Pub/Sub, and Azure Event Hubs.
What you can do after
Evaluate managed, on-premises, and hybrid deployment choices against control, administration, scalability, interoperability, and cost.

Read how Kafka for Architects explains managed service →

Platform Engineering on Kubernetes

A managed service is a provider-operated service that abstracts the administration of its software, infrastructure, and operational components.

How it is used
Frames cloud and Kubernetes choices as a trade-off between provider-operated infrastructure and internally operated platforms.
How deep it goes
Explains bundled responsibilities, costs, benefits, and constraints, but stops short of provider-specific configuration procedures.
Examples
Uses a highly available PostgreSQL instance and managed Kubernetes offerings such as GKE, AKS, and EKS.
What you can do after
Operate managed environments by provisioning clusters, allocating resources, applying access and budget controls, and deleting unused resources.

Read how Platform Engineering on Kubernetes explains managed service →

Amazon Web Services in Action, Third Edition: An in-depth guide to AWS

A managed service is a provider-operated capability in which the provider handles defined operational responsibilities for the underlying software and infrastructure.

How it is used
Uses provider-operated databases to reduce infrastructure administration in web applications.
How deep it goes
Explains provider and customer responsibilities, compares ownership trade-offs, and stops short of general managed-service implementation beyond databases.
Examples
Uses WordPress behind a load balancer with web servers and MySQL on RDS, alongside DynamoDB administration and recovery tasks.
What you can do after
Operate managed databases by choosing an engine, configuring access, monitoring capacity, and planning backups and restoration.

Read how Amazon Web Services in Action, Third Edition: An in-depth guide to AWS explains managed service →

Also covered in

What to know first

Related concepts

Questions about managed service

What is managed service?

A managed service is a technology service for which an external provider handles specified operational responsibilities, such as managing its software or infrastructure.

Which Manning books explain managed service?

Kafka for Architects, Platform Engineering on Kubernetes and Amazon Web Services in Action, Third Edition: An in-depth guide to AWS.

What should I know before learning managed service?

Manning books that teach managed service usually introduce cloud provider first.

What is the difference between managed service and self-hosting?

A managed service is a technology service for which an external provider handles specified operational responsibilities, such as managing its software or infrastructure. Self-hosting is deploying and operating software on infrastructure controlled or managed by the person or organization using it.

What kinds of managed service are there?

Kinds of managed service include Amazon Relational Database Service (RDS), GitHub Actions and DynamoDB.

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.