A municipal newsroom’s microservices on Azure Container Apps need service invocation and pub/sub without each team writing a custom HTTP client mesh. What is the appropriate way to add those building blocks?
Select an answer to reveal the explanation.
Short Explanation
Dapr on Container Apps is like plugging a shared intercom into each apartment instead of every neighbor wiring their own phones. You flip on the sidecar features for invocation and pub/sub—you do not rebuild the whole block as AKS just to get the intercom.
Full Explanation
Azure Container Apps can attach Dapr as an optional integration that runs as a sidecar and exposes building blocks such as service invocation and pub/sub. That keeps microservices on Container Apps without requiring each team to invent a custom mesh client. Migrating to AKS solely to run Dapr operators, or substituting Logic Apps or Redis, is outside the intended Container Apps pattern for this skill.