GCP Resource hierarchy

Hello and welcome back!

In this lesson, we will explore the concept of the Google Cloud Platform (GCP) resource hierarchy and understand how it efficiently organizes your cloud resources into a structured, hierarchical model. This approach ensures better management, security, and scalability for all your cloud workloads.

Hierarchical Structure Overview

GCP organizes resources into a tiered hierarchy consisting of three primary levels: organizations, folders, and projects.

• Organization:
  The organization resource is at the top of the hierarchy and represents an entire company or legal entity. It serves as the root node for all subsequent resources.

• Folders:
  Folders provide an optional layer of grouping below the organization level. They can be used to separate different legal entities, departments, or teams, thus establishing clear isolation boundaries.

• Projects:
  Projects are the foundational level where you deploy your resources, including Kubernetes clusters, virtual machines (VMs), SQL databases, and more. Each project represents a unique workspace for your cloud workloads.

Real-World Example: Pharmaceutical Company

Let's apply the resource hierarchy model to a pharmaceutical company use case. This example illustrates how an organization can be structured to support diverse departments while maintaining accountability and ease of management.

On the left side of the diagram below, you see a visual representation of an organization's structure using the resource hierarchy model. On the right side, the same hierarchy starts with the organization as the root node.

This pharmaceutical company serves as the central node in our GCP setup.

Within this organization, various key departments are represented as folders. For example, departments such as Production & R&D, Logistics, and future departments act as individual folders. The Production & R&D folder is further subdivided into development and production projects, each containing specific resources like VMs, firewalls, Kubernetes clusters, SQL databases, etc.

This structured approach allows the company to scale operations effectively, providing every team with a dedicated GCP environment. Moreover, it supports a microservices architecture by ensuring a clear separation of concerns, which not only fosters innovation but also simplifies cost tracking for deployed resources.

The diagram below further illustrates the organizational setup within our pharmaceutical company, emphasizing the hierarchy of folders, projects, and resources.

That concludes this lesson. We hope you now have a clear understanding of the GCP resource hierarchy and how it can be applied effectively using a real-world example from the pharmaceutical industry.

Thank you for reading, and see you in the next article!