Azure Container Instances

Video Activity
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *
or

Already have an account? Sign In »

Time
14 hours 28 minutes
Difficulty
Intermediate
CEU/CPE
15
Video Transcription
00:00
>> Hello, Cyberians.
00:00
Welcome to lesson 5.2 of Module 5 of this cost titled,
00:00
AZ 301 Microsoft Azure Architect Design.
00:00
Here are the objectives that we'll cover in this video.
00:00
We'll start by talking about
00:00
>> container options in Azure.
00:00
>> Just a general awareness of
00:00
>> the different options that we
00:00
>> have when we're thinking
00:00
about hosting containerized applications.
00:00
We'll then cover an introduction
00:00
of Azure Container Instances.
00:00
We'll discuss the use cases of ACI,
00:00
we'll talk about advanced features
00:00
and functionalities of the service,
00:00
and finally, we cover some limitations of the service.
00:00
What is the ACI cannot do and where you need
00:00
to consider other container hosting options in Azure.
00:00
Let's start by talking about
00:00
>> container options in Azure.
00:00
>> As you may have noticed Azure is an open Cloud that
00:00
offers multiple choices for
00:00
achieving the same end result,
00:00
which means that you can achieve the same thing in
00:00
multiple ways and with different services.
00:00
This is especially true
00:00
for containerized application scenarios.
00:00
For example, we have the following services in
00:00
Azure that allows us to run containerized applications.
00:00
We have the Azure Container Instances,
00:00
we have Azure Kubernetes Service,
00:00
we have Azure Service Fabric,
00:00
we have App Service,
00:00
we have the Batch Service,
00:00
and we have the Azure function app.
00:00
Now, a service may provide
00:00
functionalities that may not be
00:00
available in other services,
00:00
and for this module will focus on the options
00:00
that we need to know for the AZ 301 exam,
00:00
which are the Azure Container Instances,
00:00
Azure Kubernetes, Service,
00:00
Service Fabric, and a little bit of
00:00
Azure App Service running containerized applications.
00:00
Let's look at Azure Container Instances.
00:00
Azure Container Instances offer
00:00
the fastest and simplest way to run a container in
00:00
Azure without having to manage
00:00
any virtual machines and without
00:00
having to deploy Kubernetes clusters.
00:00
We simply present a container image
00:00
to the service and it runs it,
00:00
it's as simple as that,
00:00
think about ACI as
00:00
a server-less container on-demand service.
00:00
We can focus on developing our continents,
00:00
not worrying about the underlying infrastructure.
00:00
It supports my Carbonian,
00:00
which means we'll pay based on CPU and memory consumed,
00:00
which is built by the second,
00:00
so that we can fine-tune spending based on actual need.
00:00
Also Azure Container Instances
00:00
enables us to expose our continents directly to
00:00
the Internet with an Internet
00:00
>> routable public IP address
00:00
>> and a fully qualified domain name.
00:00
It also support integration with other Azure services
00:00
like Azure Container Registry that we
00:00
discussed earlier in this module,
00:00
and Azure Kubernetes service
00:00
that we'll discuss later in this module.
00:00
We'll actually be talking more about
00:00
the integration with AKS lesson.
00:00
Let's look at some of the use cases
00:00
for Azure Container Instances.
00:00
Azure Container Instances is a great solution for
00:00
scenarios that can operate in isolated continuous,
00:00
that's a big thing to emphasize,
00:00
scenarios that can operate in isolated continuous.
00:00
This includes simple applications
00:00
like applications that do data processing,
00:00
task automation, or even build jobs.
00:00
It's also good for scenarios
00:00
like event-driven application scenarios,
00:00
where we want to run a container based on
00:00
an events to complete a few activities.
00:00
It also as a good use case for
00:00
elastic Boston for workloads
00:00
that are running on Azure Kubernetes Service.
00:00
We'll look into this a bit more.
00:00
Here's a sample architecture where
00:00
Azure Container Instances is
00:00
implemented as a front end and also in the back-end.
00:00
A front-end application, it's
00:00
running in Azure Container Instance,
00:00
and that can be triggered by
00:00
an HTTP request from a customer.
00:00
There's also a containerized application
00:00
hosted on ACI in the back-end that can be
00:00
triggered by an Azure function
00:00
and the application itself can
00:00
interact with other Azure services like Cosmos DB.
00:00
Let's look at some of the advanced features
00:00
of Azure Container Instance.
00:00
Azure Container Instance supports
00:00
the shuttling of multi-continent
00:00
>> groups they are called.
00:00
>> What that essentially means is that
00:00
the containers share an hosting machine,
00:00
local network, storage, and lifecycle.
00:00
What this does is it enables us to combine
00:00
our main application container with
00:00
other supports invoke continents.
00:00
It also supports the managing of
00:00
state with Azure File Services.
00:00
What this means if we're running
00:00
instead full containers in ACI.
00:00
We can retrieve and persist state
00:00
directly in Azure file share,
00:00
which is mounted and made available to our containers.
00:00
Azure Container Instance also as integration to deploy
00:00
images directly from Azure Container Registry.
00:00
There are some of the limitations of the ACI service,
00:00
we mentioned this a little bit earlier.
00:00
We mentioned that this is optimized
00:00
for single continulized workload.
00:00
ACI is not an orchestrator,
00:00
it's a service that can be
00:00
used to easily deployed containers.
00:00
It doesn't have traditional
00:00
>> orchestrator functionalities
00:00
>> like zero-time upgrade,
00:00
which allows us to be able to do
00:00
coordinated application upgrades and
00:00
avoid an application downtime
00:00
and even a nebulin roll back if something goes wrong,
00:00
that functionality is not supported with ACI.
00:00
Services or functionalities like service discovery
00:00
where Containers can look at each order automatically,
00:00
even if they move between host and
00:00
even if they change IP addresses,
00:00
that's also not supported.
00:00
Features like integrated load balancing,
00:00
auto-scaling where Container Instances
00:00
can be added or removed to match
00:00
the demand of the workload that's coming in
00:00
that's not supported with ACI.
00:00
For scenarios where we need
00:00
>> full container orchestration,
00:00
>> it is recommended that we use
00:00
Azure Kubernetes Service, AKS.
00:00
That being said, we'll talk about
00:00
our ACI can be used by other services that
00:00
has full orchestration capabilities like
00:00
AKS and we'll talk about that in our lesson on AKS.
00:00
This brings me to the hand of this lesson,
00:00
thanks very much for watching,
00:00
and I'll see you in the next lesson.
Up Next