Send us a text

Reviewing What Not to do with Google Cloud Functions and Cloud Run

Episode 1: Show Notes.

(Recorded October 28, 2021)

Welcome to the very first installment of Cloud Out Loud! For our first show, we catch up on some recent news, including our thoughts on Facebook’s ambitious plans for their new metaverse and its accompanying data requirements. Next, we dive into our main topic, namely some of the new developments regarding Google Cloud Functions and Google Cloud Run. We take a look at recent blog posts from Google Cloud Next and discuss what they reveal about data storage and the future of Google Functions and Google Cloud Run. Our conversation also touches on Google’s presence in the cloud and data space, how they measure up against other behemoths like Amazon and Facebook, and why the way Google approaches storage through a system called Colossus is profoundly different from other players in the field. We wrap up our discussion with some thoughts on web three along with a sneak peek into future episodes. For all this and much more, tune in today!

Key Points From This Episode:

• A recap of the news of the week including an update on Cloud Next and our thoughts on some of the product announcements.
• Facebook’s ambitious metaverse and its accompanying data challenges.
• The two blog posts that Google released about Cloud Functions.
• How these blog posts inform a discussion on Cloud Functions versus Cloud Run.
• The two blog posts on avoiding GCF anti-patterns.
• How to write event-driven Cloud Functions properly by coding with idempotency in mind.
• How to reuse Cloud Function instances for future invocations.
• The trade-off between speed of execution, running out of memory, and unintentionally bloating yourself. 
• The convergences between Cloud Functions and Cloud Run.
• Some of the separate use cases for these two products.
• Our predictions for Cloud Functions and Cloud Run remaining separate products.
• Some quick thoughts and opinions from our hosts on web three.

Tweetables:

“The way Google stores things through a system called Colossus is profoundly different from everybody else. And Google had to develop this Colossus because they encountered huge amounts of data early on.” — @JonGal [0:05:03]

“We do see some convergence with Cloud Functions and Cloud Run. But they still are, I believe, separate use cases for these two products…” — @LoganAct2 [0:20:29]

Links Mentioned in Today’s Episode:

The Paper Jeff Barr tweeted about

Google Cloud Functions

Google Cloud Run

Google Cloud Next

Avoiding GCF anti-patterns part 1: How to write event-driven Cloud Functions properly by coding with idempotency in mind

Avoiding GCF anti-patterns part 2: How to reuse Cloud Function instances for future invocations

BigQ