Google Cloud Run runs stateless containers, serverlessly

try {
threshold : 0, // You can set threshold on how close to the edge ad should come before it is loaded. Default is 0 (when it is visible).
forceLoad : false, // Ad is loaded even if not visible. Default is false.
onLoad : false, // Callback function on call ad loading
onComplete : false, // Callback function when load is loaded
timeout : 1500, // Timeout ad load
debug : false, // For debug use : draw colors border depends on load status
xray : false // For debug use : display a complete page view with ad placements
}) ;
catch (exception){
console.log(“error loading lazyload_ad ” + exception);

Google has expanded its serverless compute options with the addition of Cloud Run, a managed compute service that lets you run stateless containers that are invocable via HTTP requests. Cloud Run is also available on Google Kubernetes Engine (GKE), allowing you to run containerized HTTP workloads on a managed Kubernetes cluster.

Cloud Run lets developers take advantage of the portability of containers and the velocity of serverless computing. Now in beta, Cloud Run provides for automated provisioning and scaling of workloads, with users paying only for the resources their containers actually use. On GKE, Cloud Run allows stateless HTTP workloads to run on existing Kubernetes clusters, with users having access to custom machine types, Google Compute Engine networks, and the ability to run side-by-side with other workloads in the same cluster.

Cloud Run allows developers to build applications in any language, using the tools and dependencies of their choice. Cloud Run is based on , an open API and software layer that lets users move “serverless” workloads across Kubernetes platforms including Google Cloud Platform, GKE, and anywhere else that Kubernetes runs.

Key features of Cloud Run include:

  • A command line and user interface for deploying and managing services.
  • Autoscaling, moving up and down from zero to N based on traffic. When running on GKE, autoscaling is limited to the capacity within the cluster.
  • Users can select their own language or operating system libraries as well as use their own binaries.
  • Container workflows and standards can be leveraged. Cloud Run can be paired with , , and , among others.
  • Redundancy is provided. Services are regional and automatically replicated across multiple zones.
  • Integrated logging and monitoring, including Stackdriver monitoring, logging, and error-reporting.
  • Users can map services to their own domains.

Cloud Run shares core infrastructure with two other serverless technologies at Google, and . You can go to the to start a free trial.