Cloud Computing Playbook: 10 In 1 Practical Cloud Design With Azure, AWS and Terraform

Автор: literator от 21-04-2023, 17:43, Коментариев: 0

Категория: КНИГИ » СЕТЕВЫЕ ТЕХНОЛОГИИ

Cloud Computing Playbook: 10 In 1 Practical Cloud Design With Azure, AWS and TerraformНазвание: Cloud Computing Playbook: 10 In 1 Practical Cloud Design With Azure, AWS and Terraform
Автор: Richie Miller
Издательство: Pastor Publishing
Год: 2023
Страниц: 886
Язык: английский
Формат: pdf, epub
Размер: 10.2 MB

If you want to pass the Microsoft Azure AZ-900 EXAM, or want to become an AWS certified cloud practitioner, and/or want to discover how to automate your infrastructure on any cloud with Terraform, this book is for you!

In the Book 1, we're going to talk about the exam and how to prepare for it. We will first cover the benefits of getting Azure certified and why you should consider getting the certification. We will then do an overview of the certification exam, what you will be evaluated on, as well as learn about the skills measured document. Finally, we will do an overview of our learning materials for this exam. By the end of this book, you will know what's needed to start studying for the Microsoft Certification exam. Let's start by learning what are the benefits of getting Azure certified and, more particular, why the exam. Let's start by asking, why do we even want to get a Microsoft certification? First of all, Microsoft certifications can really help give you a professional advantage by providing globally recognized and evidence of mastering skills in a digital and cloud business.

Containers are a way to wrap up an application into its own isolated package. It's for applications and services, so web apps are a typical example. When an app is deployed using a container, everything the application needs to run successfully is included in the container, like runtimes and library dependencies. This makes it easy to move the container around from your local workstation to VMs in your environment that have the container runtime installed or to a managed container hosting service in Azure, like Azure Container Instances or the Azure Kubernetes Service. The main characteristic of a container is that it makes the environment the same across different deployments, so containers reduce problems with deploying applications. Let's talk about how containers are different from virtual machines. Virtual machines run on some sort of infrastructure, whether it's your laptop or it's a physical server in a datacenter in Azure. There's a host operating system that might be Windows, Linux or macOS. Then we have a hypervisor layer, and this is what runs the virtual machine and provides resources to it from the host operating system. is Microsoft's hypervisor technology, but there are others like VMware and KVM.

Then there's the virtual machine. The virtual machine contains a full copy of an operating system, and it virtualizes the underlying hardware, meaning the CPU, memory, and storage. It also contains the application that you want to run. If you want true isolation of your applications, you'll have a copy of a VM for each application that you deploy, and that VM will need to have all the runtimes and libraries installed that the application needs. If you want to run three applications in isolation, then you'd be running three virtual machines on this hardware, each with a guest operating system that might be 800 MB in size, and each VM would require a certain amount of CPU and memory allocated to it because, again, virtual machines virtualize the hardware. Containers, on the other hand, virtualize the operating system. The host could be a physical or a virtual server, and on top of the operating system there's a runtime. This is kind of like the hypervisor for virtual machines, but it's for containers. On top of the runtime are the containers, which just contain the application along with any dependencies for that application, like frameworks and libraries for connecting storage, for example.

Container images get stored in a container registry. A container registry is a service that stores and distributes container images. Docker Hub is a public container registry on the web that serves as a general catalog of images. Azure offers a similar service called Azure Container Registry, which provides users with direct control of their images, integrated authentication with Azure AD, and many other features that come along with its Azure integration. I just mentioned Docker Hub. A Docker container is a standard that describes the format of containers and provides a runtime for Docker containers. Docker is an open source project that automates the deployment of containers that can run in the cloud or Docker is also a company that promotes and evolves the technology, and they work in collaboration with cloud vendors like Microsoft. Docker has a runtime process that you can install on any workstation or VM, and there are services in Azure that provide that runtime for you. Remember that containers are portable, so they can be moved around to different hosts.

Azure has a number of products for networking that allow you to create secure networks for your virtual machines and other Azure resources so those resources can communicate with each other and with the internet. The underlying physical network and components are managed by Microsoft, and you configure virtual versions of everything that you need. An Azure virtual network is a fundamental building block for your private network. A VNet enables many types of Azure resources to communicate. A virtual network has an address space that you define in Azure, which is a group of IP addresses that can be assigned to resources like virtual machines. A VNet is segmented into one or more subnetworks called subnets, which are allocated a portion of the VNet's IP address space. Then you deploy Azure resources to a specific subnet. A VM is assigned to a subnet, and VMs can communicate with other VMs on the same network. But you can apply security rules to that traffic using network security groups, or NSGs. These allow you to filter network traffic by allowing or denying traffic into and out of the subnet. Virtual machines are deployed into virtual networks, but you can also deploy other Azure resources into a VNet, networking components, like Azure Firewall, Application Gateway, and VPN Gateway. You can deploy resources like Redis Cache and Azure SQL Managed Instances, and analytics resources, like Azure HDInsight and Azure Databricks. And Azure Kubernetes Service gets deployed into a VNet also. You can also configure App Services to have a private IP on your VNet, which enables private connections to App Services, which have traditionally only been available over the internet.

10 books in 1 deal!


Get this book now and become a Cloud Pro today!

Скачать Cloud Computing Playbook: 10 In 1 Practical Cloud Design With Azure, AWS and Terraform








Нашел ошибку? Есть жалоба? Жми!
Пожаловаться администрации
Уважаемый посетитель, Вы зашли на сайт как незарегистрированный пользователь.
Мы рекомендуем Вам зарегистрироваться либо войти на сайт под своим именем.
Информация
Посетители, находящиеся в группе Гости, не могут оставлять комментарии к данной публикации.