Eventarc lets you build
[event-driven](https://docs.cloud.google.com/eventarc/advanced/docs/event-driven-architectures.md.txt) and
message-based architectures without having to implement, customize, or maintain
the underlying infrastructure.

Eventarc is offered in two editions: **Eventarc Advanced**
and **Eventarc Standard** . Both editions offer a scalable, serverless,
and fully managed eventing solution that lets you asynchronously route events
from sources to targets. For more information, see
[Choose Eventarc Advanced or Eventarc Standard](https://docs.cloud.google.com/eventarc/advanced/docs/choose-product-edition.md.txt).

Eventarc Advanced is designed to simplify the ingestion,
orchestration, and delivery of event data through messages across applications,
services, and endpoints. Eventarc Advanced lets you collect
events that occur in a system and publish them to a central *bus* .
Interested services can subscribe to specific messages by creating *enrollments* .
You can use the bus and a *pipeline* to route events from multiple
sources in real time, publish them to multiple destinations, and optionally
transform events prior to delivery to a target.

Eventarc Advanced is ideal for organizations with complex
eventing and messaging needs, particularly those grappling with managing
numerous Pub/Sub topics, Kafka queues, or other third-party messaging
systems. By providing administrators with enhanced and centralized visibility
and control, Eventarc Advanced enables organizations to connect
multiple teams across different projects.

You can manage Eventarc Advanced from the Google Cloud console, from
the command line using the Google Cloud CLI, or by using the Eventarc API.
[![Eventarc Advanced lets you receive, filter, transform,
route, and deliver messages between different services, apps, and systems.](https://docs.cloud.google.com/static/eventarc/images/eventarc-advanced-b440603249.svg)](https://docs.cloud.google.com/static/eventarc/images/eventarc-advanced-b440603249.svg) Eventarc Advanced lets you receive, filter, transform, route, and deliver messages  
between different services, apps, and systems (click diagram to enlarge).

## Key concepts

1. A **bus** provides a discoverable endpoint for events and is a router
   that receives all events published by providers and delivers them to zero or
   more destinations. A bus lets you centralize, monitor, and trace the
   flow of messages through your system. You can use a bus to route events
   from many sources to many targets.

2. Messages that arrive at a bus are evaluated according to the criteria
   of an **enrollment** which represents a subscription for events collected by a
   particular bus. The events are routed to consumers who have subscribed to those
   specific events. The enrollment lets you use
   [Common Expression Language (CEL)](https://docs.cloud.google.com/eventarc/advanced/docs/receive-events/use-cel.md.txt)
   to define fine-grained access control policies by matching events based on event
   attributes. An enrollment also lets you specify the pipeline to which matched
   events should be delivered.

3. The **pipeline** is the delivery intermediary between a bus and a destination.
   The pipeline specifies a target destination and also provides the option of
   transforming any matched events prior to delivering them to the destination. It
   lets you handle different event structures by supporting multiple payload
   formats and by letting you adapt event data on the fly without modifying your
   source or target services.

## Key capabilities

Eventarc Advanced supports many use cases for destination
applications. Some key capabilities are:

- **Large-scale application integration**: You can connect numerous services and
  applications, enabling asynchronous communication across different event
  formats and schemas.

- **Event streaming for AI and analytics**: You can handle the influx of data
  from IoT devices and AI workloads, filtering, transforming, and enriching events
  before feeding them into your analytics pipelines.

- **Hybrid and multi-cloud deployments**: You can extend your event-driven
  architectures beyond Google Cloud, integrating with on-premises systems and other
  cloud providers. Eventarc Advanced lets you route events from
  various sources including Google sources and direct publishers of events.

## Understand regionality

Eventarc Advanced is a fully regional service: all
Eventarc Advanced traffic and data must reside in the same
region. For example, enrollments and pipelines can only read and process data
from the same region as the bus. Cross-regional support can be achieved
by publishing events to different buses in different regions, and by
configuring a network within a
[service perimeter](https://docs.cloud.google.com/eventarc/advanced/docs/using-vpc-service-controls.md.txt) that
spans multiple regions.

## Project layouts

All Eventarc resources must belong to a Google Cloud
project. However, there is no requirement for the provider (event source),
bus (administrator), and pipeline (event target) to be in the same project. You
can also collect and publish events from Google sources in multiple projects.
For more information, see
[Publish events from multiple projects](https://docs.cloud.google.com/eventarc/advanced/docs/publish-events/publish-events-google-sources.md.txt#multiple-projects).

You can use a combination of
[Identity and Access Management (IAM) permissions](https://docs.cloud.google.com/eventarc/advanced/docs/access-control.md.txt)
to control resource usage, fine-grained access to data
[using access policies](https://docs.cloud.google.com/eventarc/advanced/docs/control-publishing-access.md.txt) and
[CEL](https://docs.cloud.google.com/eventarc/advanced/docs/receive-events/use-cel.md.txt), and
[service perimeters](https://docs.cloud.google.com/eventarc/advanced/docs/using-vpc-service-controls.md.txt) to
support networking and security requirements for different ingress and egress
needs.

## Events

An *event* is a data record that expresses an occurrence and its context, and
indicates a change in a resource or environment. An event is a discrete unit of
communication, independent of other events. For example, an event might indicate
a change to data in a database, a file added to a storage system, or a scheduled
job.

Note that an event is also a message emitted by a component when its state has
changed. When an event occurs, the message is sent to the eventing infrastructure
where consumers can retrieve it. In the context of event-driven architecture, we
often use the term *event* to refer to the message that communicates the event
rather than to the occurrence itself (what actually happened to generate the
message).

### Event types

Eventarc Advanced supports events that come directly from a
Google source.

For more information, see
[Google event types supported by Eventarc](https://docs.cloud.google.com/eventarc/advanced/docs/event-types.md.txt).

### Event providers and destinations

Events are collected from event providers by Eventarc Advanced
and routed to an event destination. Each Eventarc Advanced
pipeline can specify only one destination as its target for routed messages.

Supported providers include Google providers and direct publishers of events.
Supported destinations include Cloud Run, Cloud Run functions, HTTP
endpoints hosted in a Virtual Private Cloud network, a Pub/Sub topic,
Workflows, and another Eventarc Advanced bus.

For more information, see
[Event providers and destinations](https://docs.cloud.google.com/eventarc/advanced/docs/event-providers-targets.md.txt).

### Event format and libraries

Eventarc delivers events, regardless of provider, to the target
destination in a [CloudEvents](https://cloudevents.io/) format using an HTTP
request in binary content mode. CloudEvents is a specification for describing
event metadata in a common way.

Target destinations such as Cloud Run functions and Cloud Run
consume events in the [HTTP format](https://docs.cloud.google.com/eventarc/docs/cloudevents.md.txt). For
Workflows destinations, the Workflows service
converts the event to a [JSON object](https://docs.cloud.google.com/eventarc/docs/cloudevents-json.md.txt), and
passes the event into the workflow execution as a runtime argument.

Using a standard way to describe event metadata supports consistency,
accessibility, and portability. Event consumers can read these events directly,
or you can use the [Cloud Client Libraries](https://docs.cloud.google.com/eventarc/docs/reference/libraries.md.txt) in
various languages (including C++, C#, Go, Java, Node.js, PHP, Python, and Ruby)
to read and parse the events. There is also a set of language-specific
[CloudEvents SDKs](https://github.com/cloudevents/spec/blob/main/README.md#sdks).

The structure of the HTTP body for all events is available in the
[Google CloudEvents GitHub repository](https://github.com/googleapis/google-cloudevents).

## Reliability and delivery

There is no in-order, first-in-first-out delivery guarantee. Note that having
strict ordering would undermine Eventarc's availability and
scalability features which match those of its transport layer, Pub/Sub.
For more information, see [Ordering messages](https://docs.cloud.google.com/pubsub/docs/ordering.md.txt).

Latency and throughput are best effort. They vary based on multiple
factors, including whether publishing or egress traffic involves different
regions; the configuration of a particular service; and the network load on
resources in a Google Cloud region.

Note that there are [usage quotas and limits](https://docs.cloud.google.com/eventarc/docs/quotas.md.txt) that
apply generally to Eventarc.

### Event retry policy

The default message retention duration set by Eventarc Advanced
is 24 hours with an exponential backoff delay.

Eventarc Advanced uses an exponential backoff delay to handle
errors that can be retried. This starts with a one-second delay and the delay is
doubled after each failed attempt (up to a maximum of 60 seconds and 5 attempts).

For more information, see [Retry events](https://docs.cloud.google.com/eventarc/advanced/docs/retry-events.md.txt).

### Duplicate events

Duplicate events might be delivered to event handlers. According to the
[CloudEvents specification](https://github.com/cloudevents/spec/blob/v1.0.1/spec.md#id),
the combination of `source` and `id` attributes is considered unique, and
therefore any events with the same combination are considered duplicates.
You should implement
[idempotent event handlers](https://docs.cloud.google.com/eventarc/advanced/docs/retry-events.md.txt#idempotent-handlers)
as a general best practice.

## Observability

Google Cloud Observability provides monitoring, logging, and diagnostic tools. These tools can
help you monitor and analyze Eventarc activity and growth, and
understand the behavior, health, and performance of your applications. For more
information, see
[Observability in Eventarc](https://docs.cloud.google.com/eventarc/advanced/docs/monitor.md.txt).

Detailed logs for [Eventarc](https://docs.cloud.google.com/eventarc/advanced/docs/audit-logs.md.txt),
[Cloud Run](https://docs.cloud.google.com/run/docs/audit-logging.md.txt),
[Cloud Run functions](https://docs.cloud.google.com/functions/docs/monitoring/audit-logging.md.txt),
[Pub/Sub](https://docs.cloud.google.com/pubsub/docs/audit-logging.md.txt), and
[Workflows](https://docs.cloud.google.com/workflows/docs/audit-logging.md.txt) are
available from Cloud Audit Logs.

## Compliance standards

> [!NOTE]
> **Note:** Compliance does **not** apply to any feature in [Preview](https://cloud.google.com/products#product-launch-stages).

Eventarc Standard is compliant with specific certifications and
standards. For more information, see the
[Compliance resource center](https://cloud.google.com/compliance).

Eventarc Advanced is not compliant with the certifications and
standards that are supported by Eventarc Standard. To avoid using
non-compliant Eventarc Advanced resources, you can create a
custom organization policy that disables Eventarc Advanced
resources. For more information, see
[Disable Eventarc Advanced resources](https://docs.cloud.google.com/eventarc/standard/docs/disable-eventarc-advanced.md.txt).

## What's next

- [Quickstart: Publish and receive events by creating a bus and enrollment](https://docs.cloud.google.com/eventarc/advanced/docs/quickstarts/publish-events-create-bus.md.txt)