Managed service
A managed service is a technology service operated and maintained by an external provider, which handles defined responsibilities for its underlying software or infrastructure.
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.
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.
Related concepts
- Amazon Relational Database Service (RDS)includes · Amazon Relational Database Service is an AWS-managed service for deploying, operating, and scaling relational databases.
- self-hostingcontrasts with · Self-hosting is deploying and operating software or services on computing infrastructure controlled or managed by the user or organization.
- GitHub Actionsincludes · GitHub Actions is GitHub’s workflow automation platform for defining and running jobs in response to repository events, schedules, and other triggers.
- self-managed catalogalternative to · A self-managed catalog is a catalog whose service infrastructure and operational lifecycle are run by the organization using it.
- DynamoDBincludes · Amazon DynamoDB is a fully managed AWS NoSQL database service for storing and retrieving key-value and document data at scale.
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.