Different flavors for different situations

Both Google App Engine and Cloud Functions have different options for the different workloads that we may wish to implement. In this section, we will review the different options and consider when to use each one.

HTTP functions

HTTP functions are functions that can trigger process executions through HTTP calls, such as calls from a backend service to a cloud function. By default, and for security reasons, when a cloud function is deployed, it requires authentication from the consumer. To avoid this type of behavior, a cloud function can be deployed from the GCP console by selecting the Allow unauthenticated invocations option or by adding the allow-unauthenticated flag if the Google Cloud SDK is used. It is important to note that only cloud functions that act as public APIs should allow calls without authentication; the other APIs should always have both authentication and authorization from the consumer.

To be able to make a call...