Cognitive service in containers

---

Containers enable you to host Azure Cognitive Services either on-premises or on Azure.
Azure Cognitive Services is provided as a cloud service.
Some Cognitive Services can be deployed in a container, which encapsulates the necessary runtime components, and which is in turn deployed in a container host that provides the underlying operating system and hardware.

A container comprises an application or service and the runtime components needed to run it.
Containers are portable across hosts.
To use a container, you typically pull the container image from a registry and deploy it to a container host, specifying any required configuration settings.

• A Docker server.
• An Azure Container Instance (ACI).
• An Azure Kubernetes Service (AKS) cluster.

Deploy and use a Cognitive Services container:

• Container image for the specific Cognitive Services API you want to use is downloaded and deployed to a container host (ex: local Docker server, ACIAKS).
• Client applications submit data to the endpoint provided by the containerized service, and retrieve results (as they would be an Cognitive Services cloud resource in Azure).
• Periodically, usage metrics for the containerized service are sent to a Cognitive Services resource in Azure in order to calculate billing for the service.

Each container provides a subset of Cognitive Services functionality.

• Key Phrase Extraction
  mcr.microsoft.com/azure-cognitive-services/keyphrase
• Language Detection
  mcr.microsoft.com/azure-cognitive-services/language
• Sentiment Analysis v3 (English)
  mcr.microsoft.com/azure-cognitive-services/sentiment:3.0-en

To deploy a Cognitive Services container image to a host, you must specify:

• ApiKey
  Key from your deployed Azure Cognitive Service; used for billing.
• Billing
  Endpoint URI from your deployed Azure Cognitive Service; used for billing.
• Eula
  Value of accept to state you accept the license for the container.

Experiment source, Login to view

Resources