Book Image

Google Cloud Platform for Developers

By : Ted Hunter, Steven Porter
Book Image

Google Cloud Platform for Developers

By: Ted Hunter, Steven Porter

Overview of this book

Google Cloud Platform (GCP) provides autoscaling compute power and distributed in-memory cache, task queues, and datastores to write, build, and deploy Cloud-hosted applications. With Google Cloud Platform for Developers, you will be able to develop and deploy scalable applications from scratch and make them globally available in almost any language. This book will guide you in designing, deploying, and managing applications running on Google Cloud. You’ll start with App Engine and move on to work with Container Engine, compute engine, and cloud functions. You’ll learn how to integrate your new applications with the various data solutions on GCP, including Cloud SQL, Bigtable, and Cloud Storage. This book will teach you how to streamline your workflow with tools such as Source Repositories, Container Builder, and StackDriver. Along the way, you’ll see how to deploy and debug services with IntelliJ, implement continuous delivery pipelines, and configure robust monitoring and alerting for your production systems. By the end of this book, you’ll be well-versed with all the development tools of Google Cloud Platform, and you’ll develop, deploy, and manage highly scalable and reliable applications.
Table of Contents (17 chapters)

Integrating with other Google services

One of the primary use cases of Cloud Functions is to act as the glue that integrates various services across the GCP catalog. This is an ideal use case for Cloud Functions as there is often very little code involved and invocations can be relatively sporadic or infrequent. The default service account for Cloud Functions has project editor rights. This means that functions leveraging the default service account will automatically have authorization to act on most Google Cloud APIs.

Services may pull in any number of Google Cloud client libraries (or any npm package) as part of package.json. Once included, these libraries may be imported and used as in a traditional Node.js application.

Be careful that your application does not leverage third-party libraries in a way that creates background processes. These processes may continue across function...