Search for a command to run...
Hi! I'm Guille Ojeda, Cloud Architecture Consultant To put it simply, I create simple solutions for complex technical problems.
My focus is on designing scalable, secure, and cost-effective cloud solutions that startups, scaleups and SMBs can lean on to grow.
I lean on years of experience in cloud architecture and consulting to deliver solutions that are easy to understand and manage.
No comments yet. Be the first to comment.
What Are Agentic AI Architectures? I won't waste your time with a long, fluffy introduction about how AI is changing the world. Let's get straight to the point: agentic AI architectures are fundamentally different from the prompt-response pattern you...
Building distributed systems requires putting a lot of attention on communication between components. These components often need to exchange information asynchronously, and that's where message queues and pub/sub systems are the go-to solution. AWS ...
Database failures are inevitable. Even with the most reliable hardware and software, something will eventually break. AWS RDS Multi-AZ deployments promise to handle these failures gracefully, automatically failing over to a standby database when prob...
There are two managed relational database services in AWS: Amazon Relational Database Service (RDS) and Amazon Aurora. Both provide the benefits of a fully managed database solution, but they have distinct features and use cases. In this article, we'...
Containers offer a lightweight, portable, and scalable solution for running software consistently across different environments. But as the number of containers grows, managing them becomes increasingly complex. That's where container orchestration c...
Event-driven architectures have gained popularity in recent years, especially in conjunction with microservices. They are a type of architecture in which components respond to specific events or triggers. In cloud computing, event-driven architectures are more easily built with managed services and serverless services, making them an attractive option for businesses looking to create scalable and responsive applications.
In this blog post, we will explore event-driven architectures in Amazon Web Services (AWS), discuss some of the key benefits and challenges associated with using this approach, and provide an example implementation.
Event-driven architecture is a design pattern that allows the creation of applications and components that are triggered by specific events. These events can be external, such as a user clicking on a button, or internal, such as a record being written into a database.
In AWS, event-driven architectures are built using a combination of AWS managed services, especially Amazon Simple Queue Service (SQS), Amazon Simple Notification Service (SNS), AWS Event Bridge, and AWS Lambda.
This is an example of an event-driven architecture in AWS:
Stop copying cloud solutions, start understanding them. Join over 45,000 devs, tech leads, and experts learning how to architect cloud solutions, not pass exams, with the Simple AWS newsletter.
Scalability is one of the most significant benefits of using event-driven architectures in AWS. As these architectures are triggered by specific events, they can automatically scale up or down to meet the demands of the application. Components can also be scaled independently, helping businesses save money by only paying for the resources they use.
Event-driven architectures can also help businesses respond to customer needs more quickly. Because components are decoupled and triggered by specific events, they can be updated independently. Additionally, these architectures can integrate with a wide variety of other AWS services, enabling businesses to build complex applications that can process and analyze data from multiple sources, providing valuable insights and enabling them to make informed decisions.
One of the most significant challenges associated with using event-driven architectures in AWS is their complexity. These architectures are built using different AWS services, which can make them difficult to set up and manage, particularly for organizations unfamiliar with cloud computing and AWS architecture.
Event-driven architectures can also be challenging to test and debug. Because they are triggered by specific events, it can be difficult to simulate these events in a testing environment, making it challenging to identify and fix issues before they impact production systems.
To implement an event-driven architecture in AWS, we will use a combination of Amazon Simple Queue Service (SQS), Amazon Simple Notification Service (SNS), and AWS Lambda. It might also be useful to deploy these using AWS CloudFormation.
First, we will create an SQS queue that will act as the central hub for our event-driven architecture. This queue will receive messages whenever a specific event occurs, such as a user clicking on a button or a database reaching a certain size.
Next, we will create an SNS topic that is subscribed to the SQS queue. Whenever a message is added to the queue, the SNS topic will be notified and will trigger an AWS Lambda function.
The AWS Lambda function will contain the logic for our event-driven architecture, including processing and analyzing data, making real-time decisions, and integrating with other AWS services.
To summarize, our event-driven architecture will work as follows:
A specific event occurs, such as a user clicking on a button.
This event adds a message to the SQS queue.
The SNS topic is notified and triggers an AWS Lambda function.
The AWS Lambda function processes and analyzes the data, and takes any necessary actions.
The following CloudFormation template creates an AWS Lambda function in Node.js that is triggered by an SNS topic, which is subscribed to an SQS queue:
Copy codeAWSTemplateFormatVersion: '2010-09-09'
Resources:
MyLambdaFunction:
Type: AWS::Lambda::Function
Properties:
FunctionName: MyLambdaFunction
Runtime: nodejs12.x
Code:
ZipFile: |
exports.handler = async (event) => {
// Your function logic goes here
return
}
MySQSQueue:
Type: AWS::SQS::Queue
MySNSTopic:
Type: AWS::SNS::Topic
Properties:
Subscription:
- Protocol: sqs
Endpoint: !GetAtt MySQSQueue.Arn
This CloudFormation template creates an AWS Lambda function in Node.js named "MyLambdaFunction" and an SQS queue named "MySQSQueue". It also creates an SNS topic named "MySNSTopic" and subscribes the SQS queue to the topic.
When a message is added to the SQS queue, the SNS topic will be notified and will trigger the Lambda function. The function will contain the logic for our event-driven architecture, which you can customize by modifying the code in the "ZipFile" property.
You can also customize the properties of the SQS queue and SNS topic in the template. For instance, you can specify the visibility timeout, message retention period, and other settings for the queue. Additionally, you can modify the runtime and code for the Lambda function, as well as other properties like memory and timeout settings.
In summary, event-driven architectures in AWS offer numerous benefits, such as scalability, high responsiveness, and integration with a wide variety of AWS services. However, they also pose challenges, such as complexity and difficulty in testing and debugging. Overall, event-driven architectures can be a valuable tool for businesses looking to build scalable and highly-responsive applications in the cloud.
Stop copying cloud solutions, start understanding them. Join over 45,000 devs, tech leads, and experts learning how to architect cloud solutions, not pass exams, with the Simple AWS newsletter.
Real scenarios and solutions
The why behind the solutions
Best practices to improve them
If you'd like to know more about me, you can find me on LinkedIn or at www.guilleojeda.com