Book Image

Google Cloud Platform for Architects

By : Vitthal Srinivasan, Loonycorn , Judy Raj
Book Image

Google Cloud Platform for Architects

By: Vitthal Srinivasan, Loonycorn , Judy Raj

Overview of this book

Using a public cloud platform was considered risky a decade ago, and unconventional even just a few years ago. Today, however, use of the public cloud is completely mainstream - the norm, rather than the exception. Several leading technology firms, including Google, have built sophisticated cloud platforms, and are locked in a fierce competition for market share. The main goal of this book is to enable you to get the best out of the GCP, and to use it with confidence and competence. You will learn why cloud architectures take the forms that they do, and this will help you become a skilled high-level cloud architect. You will also learn how individual cloud services are configured and used, so that you are never intimidated at having to build it yourself. You will also learn the right way and the right situation in which to use the important GCP services. By the end of this book, you will be able to make the most out of Google Cloud Platform design.
Table of Contents (19 chapters)
13
Logging and Monitoring

Taxonomy of GCP load balancers

Each of the major cloud providers supports several different types of load balancer, and cloud architects can choose the type that best suits their use cases. Here is a taxonomy of load balancers that are available on the GCP:

As this diagram illustrates, load balancers can operate at different layers of the OSI stack. HTTP(S) load balancers operate at the application layer, SSL is a session-layer protocol, TCP is a transport-layer protocol, and network load balancers operate at the level of IP, which, of course, is a network protocol.

The rule of thumb is this: go with the highest layer of the OSI stack possible. So, for instance, if your application is based on HTTP or HTTPS, use HTTP(S) load balancing. If not, try to work at the session layer, and so on. The reason for this is the higher in the stack you are, the more real-world the abstractions...