A team wants one simple web API in a container, with built-in deployment slots. What fits?
Why B is the answer
App Service
App Service hosts containers with little to operate, and it includes deployment slots.
In detail
- App Service suits one simple API, and it has deployment slots.
- Swap slots to release with little downtime.
Use case
An illustrative scenario, not a real incident.
A team runs one simple API and wants staging swaps. App Service with deployment slots fits, with no cluster.
See it in different ways
flowchart TD
A{"What do you need?"} -->|"A simple web app in a container"| B["App Service"]
A -->|"Serverless containers, scale to zero"| C["Container Apps"]
A -->|"Full Kubernetes control"| D["AKS"]mindmap
root((Container hosting))
Container Apps
Serverless
Scale to zero
Revisions
AKS
Full Kubernetes
Node pools
App Service
Simple web API
Deployment slots
Container Registry
Stores images
Build tasksflowchart TD
Q{"What are you hosting?"}
Q -->|"One simple API"| A0["App Service"]
Q -->|"Many services"| A1["Container Apps or AKS"]Key point: App Service suits a simple web API.
Why the other options are wrong
- A. Azure Managed Redis, with the API image stored as a cached value
- Redis is a cache, not a host.
- C. A self-managed Kubernetes cluster, with an ingress controller to run
- A cluster is much more than one API needs.
- D. An Event Grid topic
- Event Grid routes events.