Please enable JavaScript.

Coggle requires JavaScript to display documents.

Google Cloud Platform, Control plane The control plane's components…

- - - - Nearline Storage
        Low cost. Good for data that can be stored for at least 30 days, including data backup and long-tail multimedia content.
      - Coldline Storage
        Very low cost. Good for data that can be stored for at least 90 days, including disaster recovery.
      - Archive Storage
        Lowest cost. Good for data that can be stored for at least 365 days, including regulatory archives.
      - Standard Storage
        Good for “hot” data that’s accessed frequently, including websites, streaming videos, and mobile apps.
    - - gsutil command
      - Drag and drop option in the cloud console
      - Storage Transfer Service
        Transfer data quickly and securely between object and file storage across Google Cloud, Amazon, Azure, on-premises, and more.
      - Transfer Appliance
        Transfer Appliance is a high-capacity storage device that enables you to transfer and securely ship your data to a Google upload facility, where we upload your data to Cloud Storage
- - - - Deployment
        
        Rolling updates
        You can perform a rolling update to update the images, configuration, labels, annotations, and resource limits/requests of the workloads in your clusters. Rolling updates incrementally replace your resource's Pods with new ones, which are then scheduled on nodes with available resources. Rolling updates are designed to update your workloads without downtime.
        
        Blue-Green deployments
        Blue-green deployment is a technique that reduces downtime/risk by running two identical production environments called Blue and Green.
        But at a given time, only one of the environments is live, with the live environment serving all production traffic. Initially, Blue is currently live and Green is idle.
        
        Canary deployments
        When we want to test a new deployment in production with a subset of our users, we can use a canary deployment. Canary deployments allow us to release a change to a small subset of our users to mitigate risk associated with new releases.
      - Architecture
  - - - App Engine standard environment
        The App Engine standard environment is based on container instances running on Google's infrastructure. Containers are preconfigured with one of several available runtimes.
        The standard environment makes it easy to build and deploy an application that runs reliably even under heavy load and with large amounts of data.
        Applications run in a secure, sandboxed environment, allowing the standard environment to distribute requests across multiple servers and scale servers to meet traffic demands. Your application runs within its own secure, reliable environment that is independent of the hardware, operating system, or physical location of the server.
      - App Engine flexible environment
        Customizable infrastructure - App Engine flexible environment instances are Compute Engine virtual machines, which means that you can take advantage of custom libraries, use SSH for debugging, and deploy your own Docker containers.
        Performance options - Take advantage of a wide array of CPU and memory configurations. You can specify how much CPU and memory each instance of your application needs, and the App Engine flexible environment provisions the necessary infrastructure for you.
        Native feature support - Features such as microservices, authorization, SQL and NoSQL databases, traffic splitting, logging, versioning, security scanning, and content delivery networks are natively supported.
        Managed virtual machines - App Engine manages your virtual machine
  - - - Zones
        Zone is an area where google cloud resources are deployed
- - - - Cloud VPN
        Cloud VPN securely extends your peer network to Google's network through an IPsec VPN tunnel. Traffic is encrypted and travels between the two networks over the public internet. Cloud VPN is useful for low-volume data connections
      - Direct Peering
        Direct Peering enables you to establish a direct peering connection between your business network and Google's edge network and exchange high-throughput cloud traffic.
        This capability is available at any of more than 100 locations in 33 countries around the world
      - Carrier Peering
        Carrier Peering enables you to access Google applications, such as Google Workspace, by using a service provider to obtain enterprise-grade network services that connect your infrastructure to Google.
        When connecting to Google through a service provider, you can get connections with higher availability and lower latency, using one or more links. Work with your service provider to get the connection that you need.
      - Dedicated Interconnect
        Cloud Interconnect extends your on-premises network to Google's network through a highly available, low latency connection. You can use Dedicated Interconnect to connect directly to Google or use Partner Interconnect to connect to Google through a supported service provide
      - Partenr Interconnect
        Partner Interconnect provides connectivity between your on-premises network and your Virtual Private Cloud (VPC) network through a supported service provider. A Partner Interconnect connection is useful if your data center is in a physical location that can't reach a Dedicated Interconnect colocation facility, or your data needs don't warrant an entire 10-Gbps connection.
- - - - Project
        The project resource is the base-level organizing entity. Organizations and folders may contain multiple projects. A project is required to use Google Cloud, and forms the basis for creating, enabling, and using all Google Cloud services, managing APIs, enabling billing, adding and removing collaborators, and managing permissions