Global HTTP(S) Load Balancing and CDN now support serverless compute

Many of you choose to develop serverless applications on Google Cloud so that you don’t have to worry about provisioning and managing the underlying infrastructure. In addition, serverless applications scale www.mcafee/activate on-demand so you only pay for what you use. But historically, serverless products like App Engine used a different HTTP load balancing system than VM-based products like Compute Engine. Today, with new External HTTP(s) integration, serverless offerings like App Engine (standard and flex), Cloud Functions and Cloud Run can now use the same fully featured enterprise-grade HTTP(S) load balancing capabilities as the rest of Google Cloud.

With this integration, you can now assign www.mcafee.com/activate product key a single global anycast IP address to your service, manage its certificates and TLS configuration www.mcafee.com/activate, integrate with Cloud CDN, and for Cloud Run and Functions—load balance across regions. And over the coming months, we will continue to add features like support for Cloud Identity-Aware Proxy (IAP) and Cloud Armor.

Introducing serverless Network Endpoint Groups

These new capabilities www.mcafee.com/activate product key are courtesy of a foundational feature of Google Cloud networking and load balancing: network endpoint groups NEGs). These collections of network endpoints are used as backend ends for www.mcafee.com/activate some load balancers to define how a set of endpoints should be reached, whether they can be reached, and where they’re located. Google Cloud HTTP(S) Load Balancing already supports a number www.mcafee/activate of different types of NEGs, like internet NEGs and Compute Engine zonal NEGs, and today, we’re expanding this list to include serverless NEGs, which allow External HTTP(S) Load Balancing to use App Engine, Cloud Functions, and Cloud Run services as backends.

Multi-region availability for Cloud Run and Cloud Functions

By integrating our serverless offerings with HTTP(S) Load Balancer, you can now deploy Cloud Run and Cloud Functions services in multiple regions. Using Cloud Run as an example, a load balancer configured with aPremium network services tier and a single forwarding rule, will deliver the request to the backend Cloud Run service closest to your clients. Processing requests from www.mcafee.com/activate product key multiple regions helps improve your service’s availability as well as response latency to your clients. Requests land in the www.mcafee/activate region closest to your users, however if the region is unavailable or short on capacity, the request will be routed to a different region.

Enabling this capability is as simple as deploying Cloud Run services to different regions, setting up multiple serverless NEGs and connecting  www.mcafee.com/activate the load balancer to global backend services.

Better performance with Cloud CDN

Cloud Run, Cloud Functions and App Engine can have cloud cdn enabled just like a Cloud Storage bucket or non-GCP backend (custom origin).

You can use the HTTP(S) Load Balancer to route static traffic to your Cloud Storage bucket and your web users or API clients to your serverless backend. This allows you to make the most of our CDN—quickly serving regularly accessed content www.mcafee/activate, closer to users—thanks to Google’s www.mcafee.com/activate product key globally distributed edge.

Alternatively, you can route all traffic to your serverless service (e.g. Cloud Run), and determine www.mcafee.com/activate download what content to cache www.mcafee.com/activate on a per-response basis  by returning appropriate cache Cache This can be great if you’re serving a public REST API from Cloud Run, and want to offload the most commonly accessed endpoints to Cloud CDN.

To use Cloud CDN with your serverless origin, simply enable Cloud CDN on the backend service that contains your serverless NEG.

SSL certificates and SSL policy management 

Both ssl certificates www.mcafee.com/activate product key management and SSL policies are now available to you for use with serverless applications. It is now easier than ever www.mcafee/activate to specify a minimum TLS version and ciphers www.mcafee.com/activate download for authenticating and encrypting traffic to your serverless applications.

The integration of HTTP(S) Load Balancing with our serverless platform also allows you to reuse the same SSL certificates www.mcafee.com/activate and private keys that you use for your domain traffic for Compute Engine, Cloud Storage www.mcafee.com/activate download and Google Kubernetes Engine (GKE). This eliminates the need to manage separate certificates.

Comments

Popular posts from this blog

Introducing tracking prevention, now available in Microsoft Edge preview builds

Why businesses need to back up

Hackers and their motives