As a Computer Engineering student, I've recently started exploring cloud computing and working toward a career in cloud engineering.
One of the first concepts I've been learning is the difference between Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS).
Understanding these three cloud service models has helped me see how cloud computing can provide different levels of control and responsibility.
Infrastructure as a Service (IaaS)
IaaS provides cloud-based infrastructure such as virtual machines, storage, and networking resources.
The main thing I learned about IaaS is that it gives the customer the most control over the infrastructure compared with PaaS and SaaS. However, that also means the customer has more responsibility for managing the environment.
For someone interested in becoming a cloud engineer, IaaS is particularly interesting because it involves working with infrastructure and understanding how different components of a cloud environment fit together.
Platform as a Service (PaaS)
PaaS provides a platform that allows developers to focus on building and deploying applications without having to manage the underlying servers and operating systems.
For example, if I wanted to create a website and focus mainly on writing and deploying my code rather than managing servers, PaaS would be a suitable model.
This showed me how cloud services can remove some of the infrastructure management responsibilities from developers.
Software as a Service (SaaS)
SaaS provides software applications that users can access without having to manage the underlying infrastructure or platform.
A simple example is using an online application through a web browser. The cloud provider manages the infrastructure, platform, and application, while the user primarily interacts with the software.
Comparing the three
The easiest way I've found to remember the difference is by thinking about control and responsibility.
IaaS → More control
PaaS → Less infrastructure management
SaaS → Mainly use the finished application
Learning these models has helped me understand that cloud computing isn't just about "storing things online." It is about providing computing resources and services in different ways depending on what the customer needs.
What's next?
I'm currently working toward my first cloud certification and exploring what it takes to become a Cloud Engineer.
My next areas of learning will include Linux, networking, cloud infrastructure, automation, and eventually DevOps technologies.
This is only the beginning of my cloud journey, but understanding IaaS, PaaS, and SaaS has given me a solid starting point.
I'm looking forward to documenting what I learn along the way.
Loading article