Phase 4: Infrastructure as Code & Cloud

Azure Essentials (AKS, Functions, Blob Storage)

Intermediate ~3 min read
Think of it this way A friendly analogy. Read this if the technical version feels dense. Show Hide

When people build amazing apps and websites, it's a bit like running a very busy, popular restaurant. You have lots of customers, different dishes to make, and you need to make sure everything runs smoothly. To help run these digital restaurants, especially when they get super big, there are three amazing secret helpers in a cloud service called Azure: Azure Kubernetes Service, Azure Functions, and Azure Blob Storage. They make sure your digital restaurant is always open, efficient, and can handle a huge rush without stress.

First, imagine your restaurant needs many cooks to prepare all the different meals. Sometimes you need more cooks for dinner rush, sometimes fewer. Azure Kubernetes Service (AKS) is like a super-smart kitchen manager. This manager makes sure all your "cooks" (which in coding are called "containers" – tiny, self-contained parts of your app) are busy. If the restaurant gets packed, AKS quickly brings in more cooks to help. When it’s quiet, it lets some cooks go home to save energy. You don't have to manage each cook; your manager handles it.

Next, some restaurant jobs are quick and specific, like a dessert specialist only baking a cake when ordered. Azure Functions are like these specialist chefs. They run tiny bits of code only when an event happens – like a new picture uploaded or a button clicked – doing their quick job and then resting, saving energy and money. Lastly, every good restaurant needs a giant pantry to store everything – ingredients, extra plates, old recipes. Azure Blob Storage is like that massive, super-organized pantry for your app. It's where you keep all the big files, pictures, and documents your app needs. It’s just for storing things, not for active cooking, and can hold a ton.

So, with this amazing kitchen manager (AKS), specialist chefs (Azure Functions), and a giant pantry (Azure Blob Storage), you can build incredible, super-efficient digital restaurants – your apps and websites! Your creation can handle thousands of people at once without slowing down, do quick, smart tasks automatically, and store all the photos and information it needs without ever running out of space. This means you can make exciting new games, social media apps, or even tools to help scientists, knowing your digital "restaurant" can serve all its customers smoothly.

As a DevOps Engineer working with Azure, understanding core services like Azure Kubernetes Service (AKS), Azure Functions, and Azure Blob Storage is fundamental to building scalable, resilient, and cost-effective cloud-native applications. These three services represent key pillars for compute and storage, enabling you to orchestrate containers, execute serverless code, and manage vast amounts of unstructured data efficiently. Mastering their practical application allows you to design robust infrastructure and streamline deployment pipelines, moving beyond basic resource provisioning to architecting complete solutions.

Azure Kubernetes Service (AKS) offers a fully managed Kubernetes environment, abstracting away the complexities of managing the Kubernetes control plane. This means you can focus on deploying and scaling your containerized applications, implementing CI/CD pipelines, and managing worker nodes, rather than the underlying cluster operations. Complementing this, Azure Functions provides a serverless compute platform, allowing you to run event-driven code snippets without provisioning or managing servers. This is ideal for microservices, API backends, data processing, or scheduled tasks that need to scale on demand and only incur costs when executed.

Finally, Azure Blob Storage delivers a highly scalable, durable, and cost-effective object storage solution for unstructured data. Whether you need to store static website content, application logs, backups, large media files, or data for analytics, Blob Storage offers various access tiers (hot, cool, archive) to optimize costs based on data access frequency. Together, AKS, Functions, and Blob Storage form a powerful toolkit for a DevOps engineer, enabling automation, efficient resource utilization, and the implementation of modern application architectures on the Azure platform.

Key Takeaways

  • AKS: Managed Kubernetes for scalable, containerized application orchestration without managing the control plane.
  • Azure Functions: Serverless compute for cost-effective, event-driven code execution, ideal for microservices and API backends.
  • Azure Blob Storage: Highly scalable and durable object storage for all forms of unstructured data (logs, backups, media).
  • Integration: These services combine to form the backbone for modern, automated, and resilient cloud-native solutions on Azure.

Code Example

bash
# Create an Azure Resource Group
az group create --name devops-essentials-rg --location eastus

# Create a Storage Account (Blob Storage)
az storage account create \
    --name devopsessentialssa \
    --resource-group devops-essentials-rg \
    --location eastus \
    --sku Standard_LRS \
    --kind StorageV2

# Create a Blob Container within the Storage Account
az storage container create \
    --name app-backups \
    --account-name devopsessentialssa \
    --public-access off # Keep it private by default

# (Optional) Upload a dummy file to the container
# echo "My backup content" > dummy_backup.txt
# az storage blob upload \
#     --container-name app-backups \
#     --file dummy_backup.txt \
#     --name backup-001.txt \
#     --account-name devopsessentialssa

echo "Resource Group 'devops-essentials-rg', Storage Account 'devopsessentialssa', and Container 'app-backups' created successfully."

How this code works

This script automates the creation of foundational Azure infrastructure for storing application backups. It establishes the necessary structure, starting with an Azure Resource Group, then provisioning a Storage Account, and finally setting up a Blob Container within that account. This structured approach helps organize and manage cloud resources effectively, preparing a designated space for application data.

The az group create command first defines devops-essentials-rg, a logical wrapper for all subsequent resources, in the eastus region. Next, az storage account create provisions devopsessentialssa, the core storage service, using StorageV2 for general-purpose use and Standard_LRS for basic data redundancy. Crucially, az storage container create then makes app-backups, the actual repository for files. The command’s public-access off setting is a vital security detail: it ensures the container is private by default, preventing unauthorized access to sensitive backup data and reinforcing secure cloud practices.

Related Articles

Hand-picked reads to go deeper on gcp / azure fundamentals.

Back to DevOps Engineer Roadmap