Cloud Solutions Architects
Designing a global infrastructure for a non-HTTP application like a mail server or IoT gateway
The TCP Proxy Load Balancing mind map provides a technical breakdown of global and regional network traffic management, specifically focusing on non-HTTP traffic architectures. This 85-node template covers 14 critical areas including 'Network tier behavior', 'Traffic allocation', and 'Session affinity'. It serves as a comprehensive TCP Proxy Load Balancing cheat sheet for cloud architects and network engineers, detailing how Google Cloud TCP Proxy Load Balancing utilizes a single global IP address to route traffic to the closest available instances. The guide explains the distinction between Premium and Standard tiers, security patching mechanisms, and the specific open ports supported, such as 25, 443, and 1883. By visualizing the relationship between forwarding rules, target proxies, and backend services, this TCP Proxy Load Balancing template helps teams design resilient N+1 or N+2 provisioning strategies.
Terms and ConditionsDesigning a global infrastructure for a non-HTTP application like a mail server or IoT gateway
Troubleshooting traffic distribution issues and understanding 'Session affinity' behavior
Preparing for a cloud networking certification exam or technical interview
Open the .xmind file in Xmind desktop or web app to view the full 85-node hierarchy of TCP proxy concepts.
Navigate to the 'Backend services' and 'Forwarding rules' branches to replace generic placeholders with your specific IP ranges and port configurations.
Use the Export function to save the 'Advantages' and 'Open ports' sections as a PDF or image for your team's internal documentation.
TCP Proxy Load Balancing is specifically intended for non-HTTP traffic. For standard web traffic, you should use HTTP Load Balancing, while proxied SSL traffic is best handled by SSL Proxy Load Balancing. This template helps distinguish these use cases clearly.
The template lists specific supported ports including 25, 43, 110, 143, 195, 443, 465, 587, 700, 993, 995, 1883, and 5222. It is a vital reference for ensuring your application protocol is compatible.
When using the Premium Tier, TCP Proxy Load Balancing acts as a global service. If you switch to the Standard Tier, it becomes a regional service where backend instance groups must be in the same region as the external IP.
Yes, the template notes that TCP Proxy Load Balancing supports both IPv4 and IPv6. Client IPv6 requests are terminated at the load balancing layer and then proxied over IPv4 to your backends.
Share your mind map templates with creators around the world and start earning from your work.