Cloud Functions 2nd gen walkthrough

Codelab → goo.gle/3kJjKaT
Quickstart → goo.gle/3FoOvLN
Read the blog → goo.gle/3P1CIr5
In a previous video, Stephanie Wong introduced Cloud Functions 2nd gen. In this video, Stephanie will take a deeper dive into Google Cloud's 2nd generation Functions-as-a-Service offering. How does it work and, more importantly, how can you take advantage of this functionality as a serverless developer? Watch along and get started with Cloud Functions 2nd gen.
Chapters:
0:00 - Intro
0:55 - Powered by Cloud Run
1:31 - Longer processing times
2:50 - Greater compute power
3:29 - Traffic splitting
5:21 - Concurrency
7:06 - Min instances
8:05 - 90+ native event integrations
9:50 - Conclusion
Subscribe to Google Cloud Tech → goo.gle/GoogleCloudTech​

[@ravichanderkt326]

Thanks for the traffic splitting, eventarc demo. I was looking out for this long time.

[@obscurecloud5575]

This is great! Thank you so much! Looks like the lines between cloud run and cloud functions are getting more blurry

[@dheer211]

Very nice insight into 2nd Gen Cloud Functions thanks Stephanie

[@sabihass5361]

Clearly explained, thanks! :)

[@omarlx]

Congratulations great job!!! Progressive deployment it's amazing

[@JeanPhilippeVAY]

Cristal clear thank you

[@matthewbeardsley7004]

Concurrency is great, really looking forward to that for HTTP requests. Global edge functions would be great as others have mentioned... :-)

[@julioconradomarinardila3269]

Excelente sistema para el trabajo en la nube

[@victoranosike2621]

Doesn't concurency affect CPU utilization of the one instance running the concurrent requests heavily?

[@thedude00]

Great video. What is the pricing model? When 2nd gen was first announced, I couldn't find this clearly stated anywhere in the blog posts or documentation.

[@WaxN-ey6vj]

According to the official. Cloud Functions (2nd gen) pricing is based on Cloud Run pricing. For information about Cloud Run pricing, see the Cloud Run Pricing page.

[@rickharold7884]

Super cool

[@HelloJaewon]

In my opinion, some features such as longer processing time, greater compute power seem to be not a great improvement compared to 1st gen. I think this is just configuration changes. Why they announced these as new feature in 2nd gen? Anyway, this is great video describing google cloud functions. Thank you.

[@epoolranggi5480]

it is because 1st gen can't be configured to the new compute power. and the long processing power can't be configured to 60 minutes. so it is a new feature to be highlight.

[@juanluislopez8292]

2nd gen for firebase functions? Any other language support?

[@riscnx]

So no improvement in cold start time? Just concurrency support, which should have always been there for NodeJS at least.

[@nishitkumar7650]

need a tutorial video on deploy nodejs app on cloud run

[@shubhamchaudhari6884]

Please allow us to use custom images for Cloud Functions!! Edit: please tell me if I'm missing any workaround.

[@riscnx]

Are you doing it for binary library support? Forget it. Come to AWS.

[@Derealsal_it_onez]

保守的發展是代碼厭倦的親切價值神經支配😍🥰😘❤️👍🏿

[@baharstudio5629]

how I got job in google ?

[@baharstudio5629]

@@juliogadiolisoares3157 thanks

[@seanknowles9985]

Pretty slow to release updates, why aren't firebase functions updated yet? Also developing locally you need to deploy a package.json and node modules per function pretty ridiculous. Lastly, where are the global edge functions to compete with AWS lambda at the edge? It's an okay update, but honestly still way behind the competition.

[@acyutanand]

Why does developer need to port their code from 1 to 2. It should happen automatically.

[@Danny-qh4su]

Gcloud is THEcloud

[@jesselima_dev]

\o/

[@dzivojelic]

Very bad experience with function unfortunately hard to test lack of emulators for services no https support in emulator overall use azure or aws

[@nickjunes]

Too bad you don't say anywhere that if you have config variables anywhere in a file, even if it's not within the v2 function it will trigger some port container error message that has nothing to do with the actual problem. I spent 2 days trying to figure this out. You really need to put a note about this in your upgrade guide. It's not intuitive at all that if you have any v1 functions still using the . config style config then it keeps the v2 functions from deploying properly and gives you a PORT error even if the v2 function body has NO .config in it. Come on guys this is a huge gotcha. At least have an appropriate error message.

[@FreeMusic54]

I'm sorry but I cannot concentrate.