Study Guides/AWS Cybersecurity Notes/AWS EventBridge: Difference between revisions
From Cramsession
Jump to navigationJump to search
✍️ Verified Author: Mflavell • Click to view professional profile & credentials
No edit summary |
|||
| Line 27: | Line 27: | ||
::* Producers - generate events. | ::* Producers - generate events. | ||
:: ⬇️ | :::: ⬇️ | ||
::* Event bus - communcation channel | ::* Event bus - communcation channel | ||
:: ⬇️ | :::: ⬇️ | ||
::* Consumers - resond to events. | ::* Consumers - resond to events. | ||
==== Why EDA ==== | |||
::* Scaleable | |||
::* Flexible | |||
::* Responsive | |||
::* Resilient | |||
Revision as of 00:36, 6 June 2026
AWS Eventbridge
Eventbridge enables imlementation of loose coupling.
- Services have little dependnece on each other.
- Changes to one component does not have a massive impact on the other.
- Provides greater flexability.
Eventbridge is serverless.
- Allows you to connect aws services and components with 3rd party systems.
- Events are pushed to an event bus.
- Rules trigger the forwarding of events to targets.
Event Driven Architecture
The sysem responds asynconiosly.
In an event driven system there are three main components:
- Producers - generate events.
- ⬇️
- Event bus - communcation channel
- ⬇️
- Consumers - resond to events.
Why EDA
- Scaleable
- Flexible
- Responsive
- Resilient
