From the course: Using Slack and AWS EventBridge to Automate Your DevOps Tasks

Why use AWS EventBridge - Amazon Web Services (AWS) Tutorial

From the course: Using Slack and AWS EventBridge to Automate Your DevOps Tasks

Start my 1-month free trial

Why use AWS EventBridge

“

- [Instructor] I can tell you from experience that the benefits of EventBridge go far beyond large application development, and that's why I created this course. It will certainly benefit your day-to-day cloud operations, even if you manage a single account with a few resources. Take these integrations, for example. You can do a lot of tasks and also monitoring of events that take place within your account, simply by subscribing to those events and assigning targets that will take actions when they occur. When you already have microservices, if your services need to call each other back and forth, you tend to move back to a monolithic architecture of dependencies. Using events allow you to create components that listen, as opposed to stop and wait for commands. This is the difference between synchronous and asynchronous software architecture. By having your services talk to each other directly, it creates a risk that if the back end service goes down, then the front end service will likely crash. However, if you design your service to be a event-based and put EventBridge in the middle, the front end will continue to work as normal, delivering and potentially receiving messages to and from EventBridge while not necessarily being aware that the back end may be down. In addition to the software development benefits, other worth mentioning include a growing list of third-party integrations. Several AWS services can be used both as targets and also as event generators. And last but not least, simple routing and filtering of events. If you write microservices or simply have a need to automate your AWS operations and integrations with third-party vendors, EventBridge is certainly a strong consideration.

Contents