Learn the basics of private versus public clouds.
- [Instructor] So what's important in public clouds? Well first, public clouds are shared, private clouds are owned by a single entity. Keep that in mind. Public clouds are owned by folks like Amazon, Microsoft, IBM, Google. Where private clouds are yours so you build them, you own them, and you can go hug the hardware and ensures to do with what you please. There can be infrastructure as a service, software as a service and platform as a service versions of public and private clouds, keep that in mind, so there's different flavors and they do different things and it's good to identify what they are and how they play a role in the public cloud market as you start to move your enterprise into the cloud.
So these are the five characteristics and we'll start within this definition which is from 2008. This is rather dated but it's a good guide for you as you go out there and try to make your way through the public cloud marketplace. It has five characteristics. On-demand self-service. Ubiquitous network access, which means you can get to it from anywhere on the open internet. Resource pooling enables you to share resources more efficiently. Rapid elasticity, you can scale up to huge loads and only pay for the servers you use, the virtual servers you use and it's pay per use so it's basically like a utility bill like you get from a power company.
Delivery models, software as a service, websites that are in essence software that's delivered over the open internet, Google Docs, Gmail, Salesforce.com, NetSuite are all examples of software as a service. Platform as a service is private clouds that allow you to develop software and it abstracts you from the underlying platforms, typically the tools are easy to use. You can build systems using any number of languages, any types of databases and deploy them on any number of platforms.
Infrastructure as a service which we're really going to focus on in this particular course is just that, it's infrastructure. It's servers, it's storage, it's networks, it's things that we can typically leverage within a data center but they're on-demand and self-service within the public cloud provider so we'll see later on in the demo where you can actually allocate a server and allocate a storage system directly from an infrastructure as a service provider such as IBM, Amazon, Microsoft and Google. In the deployment models, there's four kinds.
Private cloud which means you own it. It's your cloud, it runs in your data center. Community cloud which means you're sharing it with known users so in other words, it could be a farm community that may leverage a particular storage cloud to store farm data. Public cloud which means it's up for anybody. Anybody with a credit card can go out there and become a customer and start using the resources. And then there's hybrid cloud which is typically going to be a mix of private and public cloud together. So infrastructure as a service is pretty much what we keep in our data centers so keep that in mind.
So a lot of people get confused by it 'cause infrastructure is confusing 'cause it applies to so much of what is IT, but consider it networks and storage systems and servers so it's compute storage, networking, it even provides security, governance, databases, all kinds of things exist in an infrastructure as a service cloud. Software as a service is pretty much an application that's delivered via a web browser. So we used to buy large enterprise systems like SAP and CRM systems like Siebel and now we leverage software as a service providers which are able to deliver these applications over the open internet.
Platform as a service is pretty much development as a service as I mentioned earlier. So in other words, where we have a language, we have a database, we have tools, and we're able to build applications in the cloud and deploy them on their platform as a service provider and it makes it easier to build and deploy these systems. And you can certainly build applications on infrastructure as a service providers as well, but platform as a service providers have a tendency to abstract you away from a lot of the underlying complexity of the platform. So examples of infrastructure as a service is Amazon Web Services.
An example of SaaS would be Salesforce.com. An example of a platform as a service player would be Google App Engine.
- Public cloud benefits
- Considering the costs
- Determining compatibility
- Assessing security and governance
- Reviewing Amazon Web Services (AWS)
- Reviewing Microsoft Azure
- Reviewing Google Cloud Platform
- Reviewing IBM Softlayer