DEV Community: ayinla gbenga michael

The core architectural components of azure

ayinla gbenga michael — Fri, 16 Jan 2026 10:34:24 +0000

Azure's core architecture combines physical infrastructure (Datacenters, Regions, Zones) with a management layer (Azure Resource Manager, Resource Groups, Subscriptions, Management Groups) for organizing and controlling cloud resources like VMs, Storage, and Networks, all built upon foundational services for Compute, Storage, and Networking to deliver scalable IaaS, PaaS, and SaaS solutions globally.

Physical Infrastructure (Global Scale)
Datacenters: Physical buildings housing servers, storage, and networking equipment.
Regions: Geographic areas containing multiple datacenters, offering low latency and data sovereignty, with paired regions for disaster recovery.
Availability Zones (AZs): Physically separate locations within a region, each with independent power, cooling, and networking, for high availability.

Management & Organization (Hierarchical)
Azure Resource Manager (ARM): The deployment and management service for creating, updating, and deleting resources.
Resources: The fundamental building blocks (VMs, databases, storage) that form your solution.
Resource Groups: Logical containers to group related resources for unified lifecycle management, access control, and billing.
Subscriptions: A logical container for resources, tied to billing and access, used to organize different environments or projects.
Management Groups: Higher-level containers that allow applying governance (policies, access) across multiple subscriptions.

Foundational Services (The Building Blocks)
Compute: Virtual Machines (VMs), Containers (AKS), Serverless (Functions).
Storage: Blob, File, Queue, Table storage, managed disks.
Networking: Virtual Networks (VNets), Load Balancers, VPNs, DNS.
These components work together, managed by ARM, to build resilient, scalable, and secure cloud solutions across Azure's global footprint.

The differences between Cloud Computing and DevOps Engineering.

ayinla gbenga michael — Thu, 15 Jan 2026 13:04:12 +0000

Cloud computing is providing online infrastructure like servers, storage, while DevOps engineering is automating the processes of building, testing, and deploying software that runs on the infrastructure, focusing on speed, collaboration, and reliability.
Cloud engineers build the environment, while DevOps engineers build the pipelines and workflows that efficiently move code into that environment, often using cloud services as their foundation, creating a symbiotic relationship.

Cloud Computing
Focus: Designing, building, and managing the underlying infrastructure (servers, networks, databases) in the cloud (AWS, Azure, GCP).
Goal: Scalable, flexible, and reliable online resources.
Key Questions: "Where will the app run?" "How do we provision resources?".
Responsibilities: Infrastructure setup, networking (VPCs, subnets), security, resource optimization.

A cloud engineer is an IT professional who is responsible for creating and maintaining cloud infrastructure and platforms for individuals or business. So, a cloud engineer is mainly responsible for various technical responsibilities under cloud computing

DevOps Engineering
Focus: Bridging development and operations, automating the software delivery lifecycle (CI/CD).
Goal: Faster, more reliable software releases and improved collaboration.
Key Questions: "How do we get code from a developer to production quickly and safely?".
Responsibilities: Building CI/CD pipelines, scripting, containerization (Docker, Kubernetes), monitoring, Infrastructure as Code (Terraform).

A DevOps engineer is an IT professional who is responsible for bridging software development, engineering, and management to make the software development process faster. So, a DevOps engineer is mainly responsible for various development and operations of software applications.