What is Eventarc?
Eventarc is Google’s service for event-driven architectures on Google Cloud. The service enables reacting to changes in cloud resources and automatically triggering actions. For example, when a file is uploaded to Cloud Storage, Eventarc can automatically start a Cloud Function for processing.
Core Features
- Declarative trigger definition for over 130 GCP event sources
- Routing to Cloud Run, Cloud Functions, and GKE
- CloudEvents standard for interoperable event formats
- Audit log-based triggers for all GCP services
- Retry logic and dead-letter queues
Typical Use Cases
File Processing: Automatic processing of files upon upload to Cloud Storage. For example, image conversion, virus scanning, or metadata extraction.
Database Reactions: Triggers on changes in Cloud SQL or Firestore. Synchronization with other systems or validation of data after writing.
Infrastructure Automation: Reaction to audit log events such as resource creation. Automatic configuration, tagging, or compliance checks.
Benefits
- No polling logic required
- Loose coupling between systems
- Scales automatically with event volume
- Standardized CloudEvents format
Integration with innFactory
As a Google Cloud Partner, innFactory supports you with Eventarc: design of event-driven architectures, implementation of event pipelines, and integration into existing systems.
Available Tiers & Options
Standard
- Fully managed
- CloudEvents standard
- Native GCP integration
- Limited event transformation
Typical Use Cases
Technical Specifications
Frequently Asked Questions
What is the difference between Eventarc and Pub/Sub?
Pub/Sub is a message broker for arbitrary messages. Eventarc is an event router that forwards Cloud Events according to the CloudEvents standard to targets. Eventarc uses Pub/Sub internally but offers declarative trigger configuration.
Which event sources does Eventarc support?
Eventarc supports over 130 Google Cloud event sources such as Cloud Storage, BigQuery, Cloud SQL, and Audit Logs from all GCP services. External events can be ingested via Pub/Sub.
Which targets can Eventarc address?
Eventarc can route events to Cloud Run, Cloud Functions (2nd Gen), GKE workloads, and Workflows. Targets must be able to accept HTTP requests.
How is Eventarc billed?
Eventarc itself is free. Costs arise for the target services used (Cloud Run, Cloud Functions) and for the internally used Pub/Sub messages.
