TechKnowSurge
VideoSecurityFree

Cloud Deployment Models

Cloud computing builds on virtualization and containerization to give organizations flexible alternatives to maintaining costly on-premises infrastructure. Modern businesses typically operate across a spectrum of service models, from fully local systems to colocation, IaaS, PaaS, and SaaS.

Complete this video to capture a CTF flag worth 1 point.

About this video

Cloud computing developed directly from the widespread adoption of virtualization and, later, containerization. Bare-metal server deployments dominated through the mid-1990s, hypervisors became mainstream around 2005, and container services gained broad traction by 2013 and 2014. Each of these shifts made it more practical to abstract infrastructure away from physical hardware, ultimately making it feasible to host services in shared, remotely managed environments rather than dedicated on-site rooms. The operational burden of on-premises infrastructure helps explain why cloud adoption accelerated so quickly. A typical server room requires climate control, uninterruptible power supplies, generator backup, redundant internet connectivity, and ongoing management—all of which compound in cost and complexity as redundancy requirements grow. For small businesses and schools with limited IT staff, that overhead is difficult to justify when third-party providers can manage those same concerns at scale and with greater reliability. Hybrid architectures have become a common middle ground, where some services run locally to serve on-site users while others are replicated or extended into the cloud for redundancy and accessibility. This approach reduces the need to build and maintain a secondary physical site while still keeping latency-sensitive or compliance-sensitive workloads close to the end user. The relationship between local and cloud-hosted services can be tightly integrated, with data and configurations synchronized across both environments. Across the industry, organizations now operate somewhere along a spectrum that runs from fully on-premises to colocation facilities, Infrastructure as a Service, Platform as a Service, and Software as a Service. Each model represents a different allocation of management responsibility between the organization and the provider, and most businesses maintain several of these arrangements simultaneously. Understanding where each service sits on that spectrum is foundational to making sound decisions about security, compliance, and operational resilience.

What you'll learn

What's covered

Cloud Computing Overview

Key terms

Cloud Computing
The delivery of computing services including servers, storage, and software over the internet on a pay-as-you-go basis.
Hypervisor
Software that creates and manages virtual machines by abstracting hardware resources.
Virtual Machine
VM
A software emulation of a physical computer that runs an operating system and applications.
Infrastructure as a Service
IaaS
A cloud service model that provides virtualized computing infrastructure over the internet.
Platform as a Service
PaaS
A cloud service model that provides a platform for developing, running, and managing applications without managing infrastructure.
Software as a Service
SaaS
A cloud service model that delivers software applications over the internet on a subscription basis.
Redundancy
The duplication of critical components or systems to increase reliability and availability.
Colocation
A data center model in which an organization rents physical space, power, cooling, and network connectivity from a third-party facility while retaining ownership of its own servers and equipment.
On-Premises
An infrastructure deployment model in which hardware and software are hosted locally within an organization's own facilities rather than in a cloud provider's data center. On-premises deployments give organizations full control over their security posture.
Containerization
A deployment model that isolates applications and their dependencies inside lightweight containers that share the host operating system kernel, enabling consistent execution across different environments without duplicating a full OS.

Topics

Cloud Computing Cloud Deployment Models Virtualization Containerization Iaas Paas Saas On Premises Infrastructure

Transcript

All this virtualization has really opened the doors to allow cloud computing.

How we got here

Back in the mid-90s, let's say '95, really the primary way that we would roll out new systems is we'd buy a server, roll it out on bare metal and set up those services. Then hypervisors came along. Well, they'd been around for a while, but they became more prevalent around the 2005 era, so we started getting hypervisors and started rolling that out. Same thing with container services: they became more popular in like 2013, 2014, that's when container services started getting really popular. By the way, these are all technologies that have been out there for a long time. They just became popular a little bit later.

What it really did is open the doors for cloud computing. A lot of people started saying, well, why are we going to roll out this whole infrastructure right here when we can start utilizing somebody else's efforts in creating data centers and creating stuff? So it really opened the doors to have cloud computing.

What it costs to run it yourself

I've worked with a lot of schools and small businesses in the past, and they have some sort of network server room that has the server that has all the services running. Of course, this server room gets hot, so we need air conditioning in it to cool it down. We're also concerned about power, so we need some sort of UPS, some sort of backup power system, to make sure that server is up and running. It also needs connectivity to the internet, so I'm going to provide some sort of internet service provider connection, and I want redundancy with it, so I'm going to have multiples there. By the way, I probably also need redundancy with the UPS. Maybe I have some sort of generator that can run if something goes offline. And also the UPSs, maybe I need to double those and double the AC unit.

So now, as you can see here, I start creating this redundancy and I create stuff so that we make sure that services are up and running, and this gets very costly. Costly from a time perspective of me managing it all, and costly from an implementation standpoint.

Now if we put this in the hands of professionals and move these services, at least the ones that we can, up into the cloud, it puts it in somebody else's hands to manage all of that. And now me, as just a single IT person that's coming out to some of these clients every other week, I'm only visiting them every other week, now it puts it in an environment that can be much easier to manage.

Hybrid deployments

A lot of times we do a hybrid with this. We have cloud services that are running up in the cloud, and then we also have local services, and sometimes those even coordinate and communicate and are linked. I've had many times where I've had local services that then get replicated up into the cloud. This is a great solution, because then I have some local services that provide services for the local people within the company, but I also have some redundancy up in the cloud, and I don't have to buy a whole new site for that redundancy.

The spectrum of models

This is all to say that there are a lot of different models with that. We started out with pretty much most people having some sort of on premise. Now there are companies that came out and said, well, let's take care of the infrastructure need, the underlying data center with the power and the AC, we'll provide all that for you. So that's collocation, and then they're responsible for those elements of it, and then what we'd do is go buy the networking and the storage and the hardware, buy the rest of it and set it up there.

But then there came out other models like infrastructure as a service, where they took care of more, and then platform as a service, where they took care of more, and then SaaS, which really has been around for a long time but is to a much greater degree now.

So really, what is all of this? I'm going to get into more of this in other lessons, but for now just realize that what we have now is this whole array, this whole different spectrum of services that we can hire out to have done for us. What we hire out might depend on what service it is and how critical it is and what our needs are, and it definitely is going to affect how we're going to go about doing business from a security standpoint. But ultimately businesses nowadays usually have a combination of these working within their infrastructure, and they have to manage all of these different relationships. Sometimes it's on premise, sometimes it's collocation or infrastructure as a service or platform as a service. They're managing all of this.

About TechKnowSurge

TechKnowSurge builds IT and cybersecurity professionals through hands-on, concept-first training built around real understanding — not memorization. Free interactive tools, structured programs, and 25+ years of real-world experience, all in one place.

Explore free tools and programs →