Here is a good video on YouTube about the basics of the Cloud. Topics such as Why public Cloud, Getting started, Features, Costs, Operations, Security, Hybrid Cloud and DeskTop as a Service. It is presented by Pluralsight author & IT Consultant Elias Khnaser. The title “The difference between MS Azure and Amzon AWS is not quite covering what you see on the video but dealing with general Cloud concepts.
Beneath you find an overview of some Cloud services. This page is meant for just a fundamental knowledge of the Cloud. In most cases when you want to do a “deep dive” a link is provided so that you can continue in your search to find the needed information.
Auto scaling – Auto Scaling helps you ensure that you have the correct number of instances available to handle the load for your application. You can create scaling groups and use scaling policies.
For example, the following Auto Scaling group has a minimum size of 1 instance, a desired capacity of 2 instances, and a maximum size of 4 instances. The scaling policies that you define adjust the number of instances, within your minimum and maximum number of instances, based on the criteria that you specify. The implementation of Auto Scaling is called
- “scale sets” and “app service” at Azure;
- “auto scaling” at AWS and Google.
Container management – Container management is a server virtualisation method in which the kernel of an operating system allows the existence of multiple isolated user-space instances, instead of just one. Such instances, which are sometimes called containers, software containers.
An example of container management is Amazon EC2 Container Service (EC2) . It is a scalable, fast, container management service that makes it to run, stop, and manage Docker containers on a cluster of Elastic Compute Cloud instances. It lets you launch and stop container-based applications with API calls, allows you to get the state of your cluster from a centralised service, and gives you access to many EC2 features.
- “container service ” at Azure;
- “EC2 container service” at AWS;
- “container engine”scaling” at Google.
Microservice – Microservices architectural style is an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweight mechanisms, often an HTTP resource API. These services are built around business capabilities and independently deployable by fully automated deployment machinery.
A microservices application is decomposed into independent components called “microservices,” that work in concert to deliver the application’s overall functionality. The term “microservice” emphasises the fact that applications should be composed of services small enough to truly reflect independent concerns such that each microservice implements a single function. Moreover, each has well-defined contracts (API contracts) – typically RESTful – for other microservices to communicate and share data with it.
- “service fabric ” at Azure;
- “cloud functions” at Google;
Predefined templates: Allows you to provision your applications using a declarative template. In a single template, you can deploy multiple services along with their dependencies. You use the same template to repeatedly deploy your application during every stage of the application lifecycle.
Example: Redhat Tomcat server Template – This template allows you to create an Red Hat VM running Apache2 and Tomcat7 and enabled to support Visual Studio Team Services Apache Tomcat Deployment or Join a Windows VM to AD Domain Template – This template allows you to join an already existing Windows virtual machine into an existing Active Directory Domain
- “Azure Quickstart templates” at Azure or
- “AWS Quick Start” at Amazon Webservices
When talking about virtual storage related to the Big-3 Cloud providers here are three solutions. Since the concept of virtual storage is rather complex, instead of showing some text and graphical overviews, I wanted to show you two videos:
Amazon – AWS elastic block store (EBS)
Microsoft storage – Azure page blobs.