Sitemap
Cognizant Servian

Cognizant Servian was formed on the deep expertise of two acquisitions: Servian and Contino. Together, we are experts in innovative data and analytics, digital, customer engagement and cloud solutions to evolve your competitive advantage.

The State of Cloud Functions (mid 19)

πŸ’¬ Google Next 19 in a Nutshell

3 min readApr 26, 2019

--

Amid the fanfare of the Google Cloud Run release were significant releases in the Cloud Functions space. This overview will get you up to speed with the latest features.

Press enter or click to view image in full size
Image from Google Cloud Platform

πŸ“ˆ Scaling Behaviour (Max Instances)

Specify the maximum number of concurrent instances for a particular Cloud Function. This allows you to throttle the number of requests you can serve to avoid depleting or overloading a downstream service’s resources.

πŸ“š Scaling Behaviour Documentation

Press enter or click to view image in full size
Image from Google Cloud Platform

πŸ†” Per Function IAM Identities

By default, all Cloud Functions share the same role derived from the same AppEngine Service Account. To accommodate the least-privilege access practice, you can now assign a named service account with the correct roles to EACH function!

πŸ“š Per Function Identity Documentation

Press enter or click to view image in full size
Press enter or click to view image in full size
Different roles, different privileges! Images from Google Cloud Platform

πŸ”‘ HTTP Auth (IAM)

For some services that call HTTP endpoints (Cloud Scheduler, Cloud PubSub, Cloud Tasks), GCP will insert an OIDC JWT token in the header on behalf of the sender so you can validate the IAM role & permissions in the receiver.

Also noteworthy, GCP services will automatically validate this token before forwarding payloads to your code (Cloud Functions & Cloud Run).

πŸ“š Cloud PubSub Push Authentication/Authorization Documentation

Press enter or click to view image in full size
Press enter or click to view image in full size
Images from Google Cloud Platform

πŸ” Serverless VPC Access

Enables you to send requests from your Cloud Function to resources in your VPC network using internal IP addresses. Just create a VPC Connector, assign your Cloud Function’s Service Account the correct role & configure it to use the VPC Connector.

πŸ“š VPC Network Access Documentation

Press enter or click to view image in full size
Image from Google Cloud Platform

🌏 New Regions

London & Hong Kong have been added!

πŸ“š Cloud Functions Location Documentation

Press enter or click to view image in full size
Image from Google Cloud Platform

πŸƒ New Runtimes

The default runtimes have been updated to newer LTS versions.
Additionally, a Java 8 runtime is available in alpha (sign up here).

πŸ“š Cloud Functions Runtimes

Press enter or click to view image in full size
Image from Google Cloud Platform

Conclusion

Most of these releases were highly requested features or shown as works in progress at Next18, so it’s good to see Google is listening and delivering.

Stay tuned for an in-depth look at FaaS on GCP and how some new libraries will positively effect future runtime support, development & portability.

Sources

πŸ“Ή What’s New in Serverless Compute? (Cloud Next β€˜19)
πŸ“š Official Cloud Functions Documentation
πŸ’» Awesome Firebase

If you found this useful, please share with your friends & colleagues.

Read more GCP insights from Servian here.

--

--

James Hegedus
James Hegedus

Written by James Hegedus

https://jthegedus.dev Prefer-er of the simple things. Go, HTMX, Tailwind, Google Cloud, Firebase, Cloudflare, self-hosting @jthegedus on all platforms.

Cognizant Servian
Cognizant Servian

Published in Cognizant Servian

Cognizant Servian was formed on the deep expertise of two acquisitions: Servian and Contino. Together, we are experts in innovative data and analytics, digital, customer engagement and cloud solutions to evolve your competitive advantage.