Home > other >  What is the difference between a Google Cloud "app" and a "project"?
What is the difference between a Google Cloud "app" and a "project"?

Time:07-06

How does an app interact with a project?

Aren't both required?

Why would I want to create one but not the other?

Is a project superior to an app? or vice versa?

Why is a project part of a configuration but not an app?

Here is some code in reference to my question:

gcloud app create --region=us-west3 --project=jddjango-tutorial 
gcloud projects create cx-0705-1 --name="JD cx test" 

CodePudding user response:

  1. According to documentation

    A project organizes all your Google Cloud resources. A project consists of a set of users; a set of APIs; and billing, authentication, and monitoring settings for those APIs.

  2. This other documentation also has a similar explanation

    Google Cloud projects form the basis for creating, enabling, and using all Google Cloud services including managing APIs, enabling billing, adding and removing collaborators, and managing permissions for Google Cloud resources.

  3. An App is a 'resource' or a 'service'. A project can have multiple Apps e.g. you can have a Cloud Run App, App Engine App, Compute Engine App under the same Project.

  4. You can think of it from the POV of

    a. A project is the root/parent node. You must create one to use any google resource/service. You also create billing for the project.

    b. Under a project, you can then create an App. When you create an App, you specify the region (refer to your example command of gcloud app create --region=us-west3)

  • Related