Cloud Architects and Infrastructure Engineers
Designing a high-availability cloud architecture that requires both internal microservices and external web traffic management
Use cases
About
The Load Balancer Forwarding Rules mind map is a technical reference covering 111 nodes of architectural data for Google Cloud infrastructure. It serves as a comprehensive Load Balancer Forwarding Rules cheat sheet for cloud architects and DevOps engineers managing traffic distribution. The template provides a detailed breakdown of how a forwarding rule and its corresponding IP address represent the frontend configuration, specifically detailing the differences between Internal forwarding rules and External forwarding rules. It maps out critical protocol support for TCP, UDP, and HTTP(S) across various tiers, including specific configurations for Network load balancers and SSL proxy load balancers. By visualizing the relationship between regional and global rules, this Load Balancer Forwarding Rules template helps teams ensure high availability and correct protocol forwarding across VPC networks.
Terms and ConditionsWhen to use this template
DevOps and Site Reliability Engineers (SREs)
Troubleshooting connectivity issues between frontend IP addresses and backend target proxies
IT Students and Certification Candidates
Preparing for a Google Cloud Professional Cloud Architect certification exam
How to use this template
Step 1
Import the template file
Download and open the .xmind file in Xmind to access the full 111-node architectural breakdown.
Step 2
Map your infrastructure
Replace the generic protocol and port placeholders with your specific application requirements for TCP, UDP, or HTTP(S).
Step 3
Export for documentation
Use the Xmind export feature to save your customized forwarding rules as a PDF or PNG for your team's technical documentation.
Frequently asked questions
In this Load Balancer Forwarding Rules mind map, a forwarding rule is defined as the frontend configuration that directs traffic to a backend service, target proxy, or target pool based on IP address, protocol, and port.
Internal forwarding rules handle traffic originating within a Google Cloud or connected network, while External forwarding rules manage traffic coming from the internet. The template distinguishes these by their scope, such as regional internal vs. global external rules.
Yes, the template includes a specific branch on 'How Network Service Tiers affect load balancers', helping you decide between Premium and Standard tiers based on global or regional forwarding requirements.
Absolutely. You can modify any of the 111 nodes, add your own project-specific IP addresses, or extend the 'Cloud IAM Conditions' branch to match your organization's security policies.
Got an inspiring template?
Share your mind map templates with creators around the world and start earning from your work.
Free template