Load Balancer of Google Cloud Platform

[mitsumi]

Load Balancer of Google Cloud Platform
MP4 | Video: AVC 1280x720 | Audio: AAC 44KHz 2ch | Duration: 1 Hour | 913 MB
Genre: eLearning | Language: English

In this lesson, we'll be talking about load balancing. We'll cover the several types of load balancers of Google Cloud Platform, and then we'll create one to see how it's actually set up.

The lecture is intended to IT Cloud Administrators, IT Security engineers, IT technicians, IT Network Administrators, all fan of the cloud technology.

The level is considering to be intermediate to advances but the author composes the lectures in a progressive way from the basic to advanced.

This course will improve your ability to manage load balancers. You will learn about effective ways to build, develop Linux instances as well Windows Server instances on Google Cloud.
You will learn how to mount Apache Web Server and how to load balance two front-end web servers of Apache.

There are three types of load balancer. We have TCP, UDP and the HTTP load balancer. In this course we focus on the options that Google classifies as network load balancers, which are the TCP and UDP load balancers.

Network load balancing allows you to balance the load of your systems based on the incoming IP protocol data, such as address, port and protocol type. They use forwarding rules that point to target pools, which list instances available for load balancing and define which type of health check should be used to determine if those instances are healthy. With network load balancing you have some options that you don't have with HTTP. For example, you can load balance based on protocols, such as SMTP or FTP, and you can also perform packet inspection, which isn't available for the HTTP load balancer. So, if you need to load balance an application that doesn't run over HTTP, then you can use either TCP or UDP.

The network load balancer works by distributing traffic among pools of instances inside of a single region. It uses forwarding rules that you create to determine which pool to send traffic to, and the load balancer uses health checks to ensure that it only sends traffic to instances that are considered healthy. The health check is based on an HTTP request. So, you'll need to ensure that your instance has at least a basic web server, even if the instance isn't being used for web workloads. Network load balancing also supports a couple of additional features, namely session affinity and auto-scaling. Session affinity means that requests from a particular client will be continually directed to the same instance, and this is useful for applications that aren't stateless.
         

               

Download link:

Só visivel para registados e com resposta ao tópico.

Only visible to registered and with a reply to the topic.

Links are Interchangeable - No Password - Single Extraction