❯ Guillaume Laforge

Cloud-Run

8 production-ready features you'll find in Cloud Run fully managed

Since we launched Cloud Run at Google Cloud Next in April, developers have discovered that “serverless” and “containers” run well together. With Cloud Run, not only do you benefit from fully managed infrastructure, up and down auto-scaling, and pay-as-you-go pricing, but you’re also able to package your workload however you like, inside a stateless container listening for incoming requests, with any language, runtime, or library of your choice. And you get all this without compromising portability, thanks to its Knative open-source underpinnings. Read more...

Serverless tip #4 — Discover the full URL of your deployed Cloud Run services with gcloud format flag

Requirements: an existing Google Cloud Platform account you have enabled the Cloud Run service and deployed already a container image One of the nice things with Cloud Run is that when you deploy your services, you get a URL like https://myservice-8oafjf26aq-ew.a.run.app/, with a certificate, on the run.app domain name, etc. You see the name of the service: myservice, the region shortcut where it was deployed: ew (Europe West), and then . Read more...

Serverless tip #3 — Use the Cloud Run button on your Git repository to deploy your project in a click

Requirements: an existing Google Cloud Platform account a Git or Github repository containing your project your project can have a Dockerfile (but not mandatory) With Cloud Run, you can easily deploy a container image and let it scale up and down as needed, in a serverless fashion: No need to focus on infrastructure (provisioning servers, clusters, upgrading OS, etc.) Your application can scale transparently from 0 to 1, and from 1 to n (no need for a pager when your app is featured on Hackernews) You pay as you go, proportionally to the usage If your project is hosted on Github, for example, how can you help users get started with your project? Read more...

App Engine 2nd generation runtimes and serverless containers with Cloud Run at Cloud Next Tokyo

Last week, I was in Tokyo for the first time, to speak at the Google Cloud Next conference. During the DevDay, I spoke about Google App Engine and its 2nd generation runtimes, and I also presented Cloud Run on how to deploy and run containers in a serverless fashion. It’s been awesome to visit Japan for the first time and get a chance to meet developers there. Here are the slides I presented: Read more...

Update on the recent serverless developments on GCP at DataXDay 2019

At DataXDay 2019, last week, I had the chance to present an updated version of my introductory talk on the serverless compute options on Google Cloud Platform. There’s always something new to cover! For instance, if I put my Java Champion hat on, I’d like to mention that there are new runtimes for App Engine standard, like the beta for Java 11, and there’s twice the amount of memory as before. Read more...

A serverless Java developer's journey

Last week at the Google Cloud Next conference, I had the chance to speak about the Java developer’s journey through the “serverless” offering of Google Cloud Platform, with my colleague Vinod Ramachandran (Product Manager on some of our serverless products): Serverless Java in 2019 is going to be ubiquitous in your favorite cloud. Well, it’s actually been 10 years since you could take advantage of Java on Google App Engine. But now you can run your apps on the brand-new Java 11 runtime. Read more...

New Serverless Solutions on Google Cloud for Functions Apps and Containers

At Voxxed Days Microservices, in Paris, I talked about the latest development in serverless solutions on Google Cloud Platform, to deploy functions, apps and even containers. I answered an interview on the theme of microservices, and how this maps to the Google cloud products. And the video of my presentation was published on YouTube: Here’s the abstract of the session: Plenty of novelties in the Serverless offering of Google Cloud Platform, whether you’re developing functions, apps or containers. Read more...