Artificial Intelligence | News | Insights | AiThority
[bsfp-cryptocurrency style=”widget-18″ align=”marquee” columns=”6″ coins=”selected” coins-count=”6″ coins-selected=”BTC,ETH,XRP,LTC,EOS,ADA,XLM,NEO,LTC,EOS,XEM,DASH,USDT,BNB,QTUM,XVG,ONT,ZEC,STEEM” currency=”USD” title=”Cryptocurrency Widget” show_title=”0″ icon=”” scheme=”light” bs-show-desktop=”1″ bs-show-tablet=”1″ bs-show-phone=”1″ custom-css-class=”” custom-id=”” css=”.vc_custom_1523079266073{margin-bottom: 0px !important;padding-top: 0px !important;padding-bottom: 0px !important;}”]

Moving Events Handling to Cloud with Google Eventarc Functionality

Google Cloud has announced the public availability of events functionality -Eventarc. Eventarc was first launched in October 2020 with an aim to trigger Cloud Run from more than 60 Google Cloud sources. In its officially announced blog, Google Cloud had mentioned that Eventarc helps devops teams to easily build event-driven applications and takes care of event ingestion, delivery, security, authorization, observability, and error handling. With the latest launch, developers can focus on writing code to handle events, while Eventarc takes care of the details of event ingestion, delivery, security, observability, and error handling.

Some of the key features of Google Cloud Eventarc are mentioned below –

Setting up File Format

What is Cloud Run in Google Cloud?

If containerization trends are understood well, you can decipher what Cloud Run is.

Google’s Cloud Run allows operations on stateless containers in a fully-managed environment. Built from open-source Knative, Cloud Run allows developer to run containers in Google Kubernetes Engine cluster with Cloud Run for Anthos. Eventarc makes it seamless to connect with existing Cloud Run services with various events from different sources.

You can understand the connection between Google Sources, Cloud Run, and Eventarc with the help of the following diagram.

5480b3d19596f0.png

With Eventarc, developers can address key use cases such as video analysis, file conversion, new user signup, application monitoring, and hundreds of others. These are performed by acting on events that originate from Cloud Storage, BigQuery, Firestore and more than 60 other Google Cloud sources.

Related Posts
1 of 785

Developers can deploy these events from 60+ Google Cloud sources (via Cloud Audit logs).

Developers can also adhere to the CloudEvents standard for all events, regardless of source, to ensure a consistent developer experience.

The service is available in five Google Cloud locations, with more coming soon. It is accessible from its own API and CLI and also within Cloud Run’s UI.

How Eventarc Works

Eventarc enables any number of use cases for applications running on Cloud.

Cloud Storage event (via Cloud Audit Logs) to trigger a data processing pipeline;

BigQuery event (via Cloud Audit Logs) to initiate downstream processing in Cloud Run each time a job is completed;

Use an event from custom sources (publishing to Cloud Pub/Sub) to signal between microservices, leveraging the same standardized infrastructure for any asynchronous coordination of services.

These include third party event sources owned by enterprise data and OSS groups such as SAP, Datadog and Github.

All events are delivered in the CloudEvents v1.0 format for cross service interoperability.

Leave A Reply

Your email address will not be published.