Welcome to another episode of Apis TechTips! A video series where we provide short excerpts from our expert-led training courses.
This episode goes through popular cloud deployment models, and comes from the course Cloud, NFV and SDN in an Hour.
We hope this Apis TechTip gave you a lot of valuable information. If you want to know more about Cloud, NFV and SDN, check out our full one-hour course.
You’ll learn about topics such as:
- An introduction to Cloud
- Cloud Virtualization
- Network Functions Virtualization (NFV)
- Software-Defined Networking (SDN)
- Containers & OpenStack
Read more about the course here: https://apistraining.com/portfolio/cloud-nfv-and-sdn-in-an-hour/
This TechTip is also part of a whole eBook of tips, all focusing on Cloud technology. We call it an eBook+ since all chapters are both text and video. If you want to read the text, you can do that, and if you want to watch a teacher tell the story, you can choose that.
All the video chapters are excerpts taken directly from our recorded lessons, so if one of them piques your interest, you can easily go to the course and dive deeper into that particular subject.
This particular eBook+ is called “Cloud Chronicles: A Journey into a Virtualized and Software-Defined World“, and you only need to CLICK HERE to request it for immediate download.
Below you can find the transcribed text for this particular TechTip.
Cloud Deployment Models
First, in the top left of the image, we have the Private Cloud, where a company has amassed so much IT stuff that they benefit from actually running it as a cloud center or as a cloud infrastructure inside that corporate network.
No one on the outside can see this. It’s just inside the company. The polar opposite of that is Public Cloud, below, where you buy all your cloud services from cloud service providers on the Internet. The ISP cloud is any Internet service provider out there, and the cloud services are most normal web services, Amazon Web services, Microsoft Azure, Gmail, Office 365, or Salesforce. Things like that.
You can also mash these two together; this is called Hybrid Cloud. In the image, this is the same company as the private cloud company, company A. Only this hybrid cloud company also has a link to buy public cloud services. Why, you say? Well, it could be for different reasons. It could be for policy or legal reasons. Maybe the company has to store some things privately, but only some things, not everything. Perhaps most of the data that it works with can actually be stored publicly, then this really makes sense.
Another reason could be what’s called cloud bursting, which is if you have a very uneven load on your resources. Maybe most of the month, you only use a small amount, and then towards the end of the month, you need much more. And after a few days, you go into the next month, and you’re back to the low level again. How would you dimension your infrastructure in your private cloud? Would you dimension it for the higher level or the lower level, or somewhere in between?
Well, if you dimension it for anything lower than the highest level, then you would crash when you come to the higher level, the higher demand. So let’s dimension it for a little bit above the lowest level, just to allow a little bit of wiggle room, and then buy the rest from a public cloud. That’s why it’s called cloud bursting. You spend most of your time inside your snug, cozy little private cloud up there. But once in a while, when you need the resources, you burst out into the public cloud.
There’s also multicloud, which is just like public cloud, only more of them, hence multi. So the company C actually buys cloud services from several cloud service providers, just to not put all the eggs in the same basket essentially.
