- Cloud Function declarations are called triggers.
- Microservices architecture based applications can be implemented entirely in cloud functions.
- Cloud Functions can be used to enhance existing applications without worry about scaling.
- Cloud Functions is a microservices architecture.
- Cloud Functions exposes a single endpoint.
- Cloud Functions backend is a single piece of code that accepts a limited input, executes rapidly, produces some output and then exits.
- There is no need to pay for servers.
- Cloud Functions users only pay whenever their functions runs, in 100 millisecond intervals.
- Cloud Functions can trigger on events in cloud storage, Cloud Pub/Sub, or a HTTP call.
- For each event type, a developer can configure a Cloud Function to trigger.
- Cloud Functions triggers can be configured using Cloud Pub/Sub, HTTP and Cloud storage.
- Cloud Functions can be deployed from a Cloud Storage bucket, Github or a Bitbucket repo.
- Cloud Functions is integrated with Operations tooling for monitoring, logging, and error reporting.