Google Professional Cloud Architect Study Guide

Chapter 2. The Virtual Private Cloud: Connecting Your Services

I was getting background information from a client one time in anticipation of my doing some training for them. I said, “Tell me about your organizational structure in Google Cloud.”

“Well,” my contact hedged, “You have to understand, our growth into Google Cloud happened organically.”

Uh-oh. You know what that means, right? For confirmation, I said, “So, you had no plan in place before the move?”

“Correct.”

By now I’m good at not rolling my eyes or, through other overt body language, telling my client that they’ve made a mistake. Since I usually have a terrible poker face, it also helps that this is a type of mistake I’ve seen and dealt with over and over.

“How many projects do you have?”

“Mmmmm, about 30,000.”

Ok, my eyes might have bugged a bit at that. Google and I are both big fans of small, purpose-built projects, but most organizations figure out they need to clean up their process and their GCP environment before they are 30,000 projects in.

I don’t even know why I asked my next question, probably morbid curiosity. “And how many networks do you have?”

Blink, Blink. “Well, 30,000; one comes in each project, right?”

30,000 default networks. Man were they doing things the hard way. They were going to be so excited when I showed them how a clean network design could not only make their GCP footprint more secure, but I was also about to save them thousands of dollars a month in networking egress and management ...