As a Software Engineer with a background in .NET and enterprise application systems, I’ve started my structured transition into Cloud & DevOps engineering.
Instead of jumping directly into advanced tools and automation, I chose to begin where every strong cloud engineer begins — the fundamentals.
Because scalable systems are never built on weak foundations.
☁️ Understanding Cloud Computing
Cloud computing is the delivery of computing services — servers, storage, databases, networking, and software — over the internet on a pay-as-you-go model.
What makes it powerful:
- On-demand resource provisioning
- Elastic scalability
- High availability
- Cost efficiency
- No physical infrastructure management
Leading cloud providers include:
- Amazon Web Services
- Microsoft Azure
- Google Cloud Platform
This shifts the mindset from simply deploying applications to designing systems that are scalable and resilient by architecture.
🏗 Cloud Service Models – Understanding Responsibility
One of the most important concepts I reinforced today was who manages what in cloud environments.
🔹 IaaS (Infrastructure as a Service)
Example: Amazon EC2
- User manages: OS, middleware, applications
- Provider manages: hardware & virtualization
🔹 PaaS (Platform as a Service)
Example: Azure App Service
- User manages: Application code
- Provider manages: OS, runtime, infrastructure
🔹 SaaS (Software as a Service)
Example: Google Docs
- Fully managed by provider
- Delivered over the internet
- No infrastructure management required
Understanding these models is critical for designing the right architecture.
🌍 Cloud Deployment Models
I also revisited deployment strategies:
- Public Cloud – Shared infrastructure (e.g., Amazon Web Services)
- Private Cloud – Dedicated infrastructure for one organization
- Hybrid Cloud – Combination of public and private environments
These models directly impact security, compliance, and scalability decisions.
☁️ Core AWS Services Reviewed
To build clarity, I focused on foundational services of Amazon Web Services:
🔹 EC2 – Compute
Amazon EC2 provides resizable virtual servers to run applications.
🔹 S3 – Storage
Amazon S3 offers highly durable object storage for files, backups, and logs.
🔹 IAM – Security
AWS Identity and Access Management controls users, roles, and permissions.
Principle reinforced:
Always follow least privilege. Never use root for daily operations.
🔹 VPC – Networking
Amazon VPC enables logically isolated networking with subnets, route tables, and security groups.
This connects cloud infrastructure directly with networking fundamentals.
🖥 Virtualization – The Backbone of Cloud
Cloud environments operate using virtualization technology. Solutions like those from VMware allow multiple virtual machines to run on a single physical server using hypervisors.
This enables efficient resource utilization, isolation, and scalability at scale.
🔍 Key Reflection from Day 1
As someone transitioning from application development to cloud engineering, I’m beginning to see how everything connects:
- Applications run on compute
- Data resides in storage
- Access is controlled through identity policies
- Infrastructure lives inside secure networks
Cloud engineering is not separate from development — it strengthens it.
Consistency remains the real superpower 💪🐧
Top comments (0)