Book Image

Building Google Cloud Platform Solutions

By : Ted Hunter, Steven Porter, Legorie Rajan PS
Book Image

Building Google Cloud Platform Solutions

By: Ted Hunter, Steven Porter, Legorie Rajan PS

Overview of this book

GCP is a cloud computing platform with a wide range of products and services that enable you to build and deploy cloud-hosted applications. This Learning Path will guide you in using GCP and designing, deploying, and managing applications on Google Cloud. You will get started by learning how to use App Engine to access Google's scalable hosting and build software that runs on this framework. With the help of Google Compute Engine, you’ll be able to host your workload on virtual machine instances. The later chapters will help you to explore ways to implement authentication and security, Cloud APIs, and command-line and deployment management. As you hone your skills, you’ll understand how to integrate your new applications with various data solutions on GCP, including Cloud SQL, Bigtable, and Cloud Storage. Following this, the book will teach you how to streamline your workflow with tools, including Source Repositories, Container Builder, and Stackdriver. You'll also understand how to deploy and debug services with IntelliJ, implement continuous delivery pipelines, and configure robust monitoring and alerts for your production systems. By the end of this Learning Path, you'll be well versed with GCP’s development tools and be able to develop, deploy, and manage highly scalable and reliable applications. This Learning Path includes content from the following Packt products: • Google Cloud Platform for Developers Ted Hunter and Steven Porter • Google Cloud Platform Cookbook by Legorie Rajan PS
Table of Contents (29 chapters)
Title Page
Copyright and Credits
About Packt
Contributors
Preface
Index

Invoking Cloud Functions


Cloud Functions are invoked by external events called triggers. These triggers relate to some external event. When the event occurs, the platform will invoke the function on your behalf. Functions can be divided into two groups based on the type of trigger used to invoke them: HTTP functions and background functions.

HTTP functions

HTTP functions are triggered remotely by performing an HTTP request on a Google provided URL. The invocation URL takes the following naming convention:

https://<REGION>-<PROJECT_ID>.cloudfunctions.net/<FUNCTION_NAME>

Note

While there is currently no direct way to modify HTTP function URLs, there are a number of methods for making functions available behind custom URLs. The simplest method for achieving this is by providing a simple forward proxy running on Compute Engine using technologies such as NGINX. Another approach is through the use of a Firebase application.

When a network request is made to this URL, the function will...