A Professional Cloud Developer builds scalable and highly available applications using Google recommended practices and tools that leverage fully managed services. This individual has experience with next generation databases, runtime environments and developer tools. They also have proficiency with at least one general purpose programming language and are skilled with using Stackdriver to produce meaningful metrics and logs to debug and trace code.
1.1 Designing performant applications and APIs.
1.2 Designing secure applications.
1.3 Managing application data.
1.4 Re-architecting applications from local services to Google Cloud Platform.
2.1 Setting up your development environment.
2.2 Building a continuous integration pipeline.
2.3 Testing.
2.4 Writing code.
3.1 Implementing appropriate deployment strategies based on the target compute environment (Compute Engine, Google Kubernetes Engine, App Engine).
3.2 Deploying applications and services on Compute Engine.
3.3 Deploying applications and services on Google Kubernetes Engine.
3.4 Deploying an application to App Engine.
3.5 Deploying a Cloud Function.
3.6 Creating data storage resources.
3.7 Deploying and implementing networking resources.
3.8 Automating resource provisioning with Deployment Manager
3.9 Managing Service accounts.
4.1 Integrating an application with Data and Storage services.
4.2 Integrating an application with compute services.
4.3 Integrating Google Cloud APIs with applications.
5.1 Installing the logging and monitoring agent
5.2 Managing VMs.
5.3 Viewing application performance metrics using Stackdriver.
5.4 Diagnosing and resolving application performance issues.
App Hosting on Google Cloud https://cloud.google.com/hosting-options/
App Engine https://cloud.google.com/appengine/
Choosing an App Engine environment https://cloud.google.com/appengine/docs/the-appengine-environments
App Engine Flexible Environment for Users of App Engine Standard Environment https://cloud.google.com/appengine/docs/flexible/python/flexible-for-standard-users
The App Engine Standard Environment https://cloud.google.com/appengine/docs/standard/
Python 3 Runtime Environment https://cloud.google.com/appengine/docs/standard/python3/runtime
Quickstart for Python 3 in the App Engine Standard Environment https://cloud.google.com/appengine/docs/standard/python3/quickstart
app.yaml Configuration File https://cloud.google.com/appengine/docs/standard/python3/config/appref
An Overview of App Engine https://cloud.google.com/appengine/docs/standard/python3/an-overview-of-app-engine
Testing and deploying your application https://cloud.google.com/appengine/docs/standard/python3/testing-and-deploying-your-app
Each time you deploy a new version, a container image is created using the Cloud Build service. That container image then runs in the App Engine standard environment.
Built container images are stored in the app-engine folder in Container Registry. You can download these images to keep or run elsewhere. Once deployment is complete, App Engine no longer needs the container images. Note that they are not automatically deleted, so to avoid reaching your storage quota, you can safely delete any images you don't need.
Structuring Web Services in App Engine https://cloud.google.com/appengine/docs/standard/python3/configuration-files
Migrating Traffic https://cloud.google.com/appengine/docs/standard/python3/migrating-traffic
Splitting Traffic https://cloud.google.com/appengine/docs/standard/python3/splitting-traffic
How Requests are Routed https://cloud.google.com/appengine/docs/standard/python3/how-requests-are-routed
How Instances are Managed https://cloud.google.com/appengine/docs/standard/python3/how-instances-are-managed
Authenticating Users https://cloud.google.com/appengine/docs/standard/python3/authenticating-users
Overview of App Security https://cloud.google.com/appengine/docs/standard/python3/application-security
Getting Started with Endpoints for App Engine standard environment https://cloud.google.com/endpoints/docs/openapi/get-started-app-engine-standard
Controlling Access with Firewalls https://cloud.google.com/appengine/docs/standard/python3/creating-firewalls
Most apps need to know the identity of a user. Knowing a user's identity allows an app to securely save user data in the cloud and provide the same personalized experience across all of the user's devices.
Firebase Authentication provides backend services, easy-to-use SDKs, and ready-made UI libraries to authenticate users to your app. It supports authentication using passwords, phone numbers, popular federated identity providers like Google, Facebook and Twitter, and more.
Firebase Authentication integrates tightly with other Firebase services, and it leverages industry standards like OAuth 2.0 and OpenID Connect, so it can be easily integrated with your custom backend.
Highlights how to use Firebase on a website, including user sign in with Google as the Identity Provider.
Cloud Build is a service that executes your builds on Google Cloud Platform infrastructure. Cloud Build executes your build as a series of build steps, where each build step is run in a Docker container.
Continuously build, test, and deploy.
Welcome to the CI/CD developer hub! Get started or deep dive with continuous integration and continuous deployment.
A build config file contains instructions for Cloud Build to perform tasks based on your specifications. For example, your build config file can contain instructions to build, package, and push Docker images.
While you can use Google Cloud APIs by making direct HTTP requests to the server (or RPC calls where available), we provide client library code for all our Cloud APIs that makes it easier to access them from your favorite languages.
Google Cloud Client Libraries are our latest and recommended client libraries for calling Google Cloud APIs. They provide an optimized developer experience by using each supported language's natural conventions and styles. They also reduce the boilerplate code you have to write because they're designed to enable you to work with service metaphors in mind, rather than implementation details or service API concepts.
Apigee Edge is a platform for developing and managing APIs. By fronting services with a proxy layer, Edge provides an abstraction or facade for your backend service APIs and provides security, rate limiting, quotas, analytics, and more.
Cloud Run is a managed compute platform that enables you to run stateless containers that are invocable via web requests or Pub/Sub events. Cloud Run is serverless: it abstracts away all infrastructure management, so you can focus on what matters most — building great applications.
https://cloud.google.com/storage-transfer/docs/overview#should_you_use_gsutil_orParallel Composite Uploads https://cloud.google.com/storage/docs/gsutil/commands/cp#parallel-composite-uploads_1
Serverless computing is a paradigm shift in application development that enables developers to focus on writing code without worrying about infrastructure. It offers a variety of benefits over traditional computing, including zero server management, no up-front provisioning, auto-scaling, and paying only for the resources used. These advantages make serverless ideal for use cases like stateless HTTP applications, web, mobile, IoT backends, batch and stream data processing, chatbots, and more.
Managing uptime checks https://cloud.google.com/monitoring/uptime-checks/
Application Performance Monitoring https://cloud.google.com/apm/
Stackdriver Trace https://cloud.google.com/trace/
https://cloud.google.com/memorystore/docs/redis/memory-management-best-practices
A Cloud Memorystore for Redis instance, if not correctly managed and configured, can experience memory pressure which can impact application performance. This page describes best practices that you can use to efficiently manage your instance's memory usage.
https://cloud.google.com/blog/products/gcp/12-best-practices-for-user-account
Account management, authorization and password management can be tricky. For many developers, account management is a dark corner that doesn't get enough attention. For product managers and customers, the resulting experience often falls short of expectations.
https://cloud.google.com/storage/docs/best-practices
This page contains a summary of best practices drawn from other pages in the Cloud Storage documentation. You can use the best practices listed here as a quick reference of what to keep in mind when building an application that uses Cloud Storage. Follow these best practices when launching a commercial application.
https://cloud.google.com/datastore/docs/best-practices
You can use the best practices listed here as a quick reference of what to keep in mind when building an application that uses Cloud Firestore in Datastore mode.
https://cloud.google.com/spanner/docs/best-practice-list
https://cloud.google.com/spanner/docs/schema-design
This page describes best practices for designing Cloud Spanner schemas to avoid hotspots and for loading data into Cloud Spanner.
https://cloud.google.com/iap/docs/concepts-best-practices
https://cloud.google.com/iam/docs/using-iam-securely
https://cloud.google.com/deployment-manager/docs/best-practices/
https://cloud.google.com/solutions/design-patterns-for-exporting-stackdriver-logging