AWS EventBridge
Question
You are working in a big organization as a DevOps engineer.
There is a monolithic application that is deployed and maintained in AWS EC2
The application needs to be redesigned to be microservices.
The new serverless event-based architecture will decouple services and components so that the application becomes more extensible.
You need a central AWS service to manage the events among application components and also allow you to receive events from third-party SaaS apps such as PageDuty.
Which of the following AWS services would you recommend in the new architecture?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.Correct Answer: D.
Option A is incorrect because the event management service needs to receive events from third-party SaaS apps so Amazon EventBridge is a better choice than CloudWatch Event.
Amazon EventBridge uses the Amazon CloudWatch Events API, but also includes more functionality.
Option B is incorrect because the microservice architecture needs a serverless computer component so Lambda function should be included.
Option C is incorrect because Amazon EventBridge and AWS Step Function are similar and both services can simplify workflows in distributed applications.
However, Lambda function should be selected to implement the application logic.
Option D is CORRECT because Amazon EventBridge can set up event rules and Lambda functions can implement various software components.
EventBridge rules can invoke Lambda functions for further processing.
Reference:
https://aws.amazon.com/blogs/compute/decoupling-larger-applications-with-amazon-eventbridge/As a DevOps engineer, you are tasked with redesigning a monolithic application into a microservices architecture using a serverless event-based architecture that will decouple the services and components. You also need a central AWS service to manage events between application components and receive events from third-party SaaS apps such as PageDuty.
Out of the given options, the most suitable AWS service for this requirement is Amazon EventBridge (formerly known as CloudWatch Events). Amazon EventBridge is a scalable event bus service that allows you to create event-driven architectures by connecting applications using data from various sources such as AWS services, SaaS applications, and custom applications. It can receive events from various sources and route them to one or more targets, including AWS Lambda functions, Amazon SNS topics, AWS Step Functions, and more.
Option A, CloudWatch Event + Lambda function, is not as suitable as Amazon EventBridge because it only supports AWS services as event sources, and it doesn't support SaaS applications. In contrast, Amazon EventBridge supports a wide range of event sources, including SaaS applications, making it a better choice for a central event management service.
Option B, CloudTrail + CloudWatch Event, is also not the best choice for a central event management service as CloudTrail only captures and logs API calls made in your AWS account. It doesn't support third-party SaaS applications, and it requires additional configuration to create event rules to trigger actions based on the captured API events.
Option C, Amazon EventBridge + AWS Step Function, is a viable option. AWS Step Functions allow you to build scalable, resilient workflows that coordinate multiple AWS services and custom applications. However, it may not be necessary for the current requirement, and it adds an extra layer of complexity to the architecture.
Option D, Amazon EventBridge + Lambda function, is the best choice for a central event management service, and it is the simplest and most straightforward option. With Amazon EventBridge and AWS Lambda, you can easily create event-driven architectures that can react to events from various sources, including SaaS applications like PageDuty.
In summary, the most suitable AWS service for managing events among application components and receiving events from third-party SaaS apps is Amazon EventBridge + Lambda function.
