Hi everyone, this time its back to some basic exploration. As we know that networking is one of the most basic infrastructure building blocks and how Google provide a global infrastructure to be used by customer. Oftenly this global infrastructure statement is not an interesting things for architect or developer until we are working with multiple regions, either for distributed system or just a plain DR site. If you are interested please go and find more on the site below:
Global Networking Products that Scale | Google Cloud
So right now I am exploring the capabilities one of the networking product which is Load Balancer.
Load Balancing | Google Cloud
If you are interested in more in-depth talks, I found one good Cloud Next session which may help to get an overview of the network capabilities: (If not just pass it through).
Now the statement of global load balancing is interesting, but to sum up, it means that the customer may have a single VIP that spans globally, and then the Load Balancer will determine the closest resources with the user and redirect the traffic over there.
I taking the use case to test it in a very simple way, where I want to create three VM which two are allocated in Jakarta Region (my current location) and one VM which are allocated in Europe which I hope is far enough.
Super simple architecture
I will try it in a very simple manner, and if you are interested to run through by yourself I am using the guide from the link below:
Setting up a simple external HTTP load balancer | Load Balancing
Preparation
[One] Create the VM using the steps from the guide. This will help to create VM instances that provide HTTP response and answering the instance name of the one who is responding. (Help us to know which instance we communicate with).
Two in Jakarta region, One in Europe or other location as you please.
Note: I am using the default vpc for simplicity.
#cloud #cloud-load-balance #gcp #google #global-infrastructure #cloud