Create event-driven architectures with Eventarc

You can use Eventarc and Firestore with MongoDB compatibility to build event-driven architectures. Firestore with MongoDB compatibility triggers for Eventarc generate events from changes to a particular documents in your database. The trigger can route events to a supported destination:

Eventarc offers a standardized solution to manage the flow of state changes, called events, between decoupled microservices. When triggered, Eventarc routes these events to various destinations while managing delivery, security, authorization, observability, and error-handling for you.

Limitations

Note the following limitations for Firestore with MongoDB compatibility triggers for Eventarc:

  • Ordering is not guaranteed. Rapid changes can trigger events in an unexpected order.

  • Events are delivered at least once.

    Make sure your event handler is idempotent and avoid producing unexpected results or side effects when an event is delivered more than once. Refer to Building idempotent functions to learn more.

  • A trigger is associated with a single database. You cannot create a trigger that matches multiple databases.

  • Deleting a database does not automatically delete any triggers for that database. The trigger stops delivering events but continues to exist until you delete the trigger. If the database is recreated, any associated triggers will also need to be deleted and recreated to restore event delivery.

  • Firestore with MongoDB compatibility supports Cloud Run functions (2nd gen) and doesn't support Cloud Run functions (1st gen).

  • Firestore Enterprise edition databases do not support Datastore entity event types.

What's next