Compute Resource
Virtual Machine
Availability set
When you host your virtual machines in Azure, you sometimes need to cater to the following
An unplanned event wherein the underlying infrastructure fails unexpectedly. The failures could be attributed to network failures , local disk failures or even rack failures.
Planned maintenance events , wherein Microsoft needs to make planned updates to the underlying physical environment. In such cases , a reboot might be required on your virtual machine.
You can increase the availability of your application by making use of availability sets. Each virtual machine that is assigned to the availability set is assigned a separate fault and update domain.
Fault domains are used to define the group of virtual machines that share a common source and network switch. You can have up to 3 fault domains.
Update domains are used to group virtual machines and physical hardware that can be rebooted at the same time. You can have up to 20 update domains.
Availability Zones
This features help provides better availability for your application by protecting them from datacenter failures.
Each Availability zone is a unique physical location in an Azure region.
Each zone comprises of one or more data centers that has independent power, cooling, and networking
VM Scale set
Define the rule to scale out (adding new vm) / scale in (reducing vm)
VM Image
A copy template of vm including data disk or just os disk
It can be used of creating another vm or vm scale set
Azure Bastion
Provide RDP/SSH connectivity to vm from portal through TLS
Prevent from exposing IP address to external
Azure Web App
Similar with GCP Cloud Run, is PAAS to let developer deploy the code or docker image easily
Auto Scale
Based the metric defined , auto scale the instance of the web app
Deployment Slots
Divided into several slots, like version 1 and version 2
Can adjust the percentage of traffic between different slots
Backup
can create the backup and store it into store account
can restore the backup to new app service
Kubernetes and Service Fabric
To build micro services
Data Factory
To create pipeline to process the data and convert data from source compute resource or storage to other destination of other compute resource or storage in different format
Logic App
To build a web flow step by step and integrate with other service , such as sending approval via gmail
Event Hub & Service Bus
Both are message brokers
Azure Event Hubs focuses more on event streaming whereas Azure Service Bus is more focused on high-value enterprise messaging, which means the later is focused on messages rather than events.
Event Grid
Mainly used for communication between azure resources
Trigger the event when there are events happened on publisher
Handled the event with azure function, logic app ,etc
Last updated
Was this helpful?