Connect to services on another VPC via Private Service Connect (PSC)

Connecting services that operate on different VPC networks in Google Cloud Platform (GCP) has always been a challenging task. Typically, organisations either have to go through the cumbersome process of aligning IP spaces in advance, which is rarely done, or they face the problem of teams being unable to connect their services due to the use of private VPCs. Both shared VPC and private VPC have their respective purposes, making it difficult to predict whether team connectivity will be necessary in many scenarios. Additionally, it is hard to anticipate if a service will need to be exposed to a larger audience in the future. This is where the PSC (Private Service Connect) feature comes into play. In my opinion, after testing it out, PSC represents a significant advancement in resolving this issue with an elegant design. In today's video, I will delve into the common issues I often encounter and explain in detail how PSC can effectively address them. I am truly enthusiastic about the potential impact this solution can have on VPC networking in the GCP ecosystem as a whole. Slides: https://docs.google.com/presentation/d/17EyWWkK-NTLPN04SWOVrvrCT1O6zmJZiP-e9UqTE-Q8/edit?usp=sharing 01:00 - The problem with cross VPC connectivity 04:12 - What is Private Service Connect (PSC)? 07:20 - Use PSC to connect to services on another VPC 10:39 - Demo 17:27 - The future design of microservices networking using PSC 19:51 - Summary