Get started with the main concepts behind Event Bridge
The main components3 of an Event Bridge are:
The main service component, the bus is responsible for receiving events and routing them to the correct targets following all applicable rules.
These are messages published by a service through the EventBridge bus. It may indicate a change in an environment, an action taken, a scheduled event occurence, or virtually anything else. Events are JSON messages that should follow a template standard to the Event Bridge Service.
Services that send events to the Bus in order to be taken care of by target services. Example: when a new customer subscribes to an online service, the subscription component (source) may need to inform other services (targets) in the system about it - to send a confirmation e-mail, for example.
Services that subscribe to the Event Bus in order to receive events when published by source components and matched by the rules in place.
A set of instructions for the Event Bus to decide whether a particular message should be delivered to certain targets. Each rule can route a matched event to one or multiple targets. Another feature of rules is that they can customize event messages, by passing to targets only a subset of the information available, for example.
Event Bridge schema is a template containing the structure expected for a certain type of event message published through an event bus. While this is an optional component for the EventBridge service, it can improve transparency and maintainability of highly complex systems running asynchronously on EventBridge.
AWS launched in Dec 2019 the Schema Registry4 service. Although still in preview5, it makes it easier to identify, document and discover event schemas within Event Bridge. The Schema Registry service can also generate schemas based on inference from events already published through an event bus.
Save time spent on debugging applications.
Increase development velocity and quality.
Get actionable insights to your infrastructure.