พื้นฐานสถาปัตยกรรมที่ขับเคลื่อนด้วยเหตุการณ์

Imagine a restaurant where orders are taken, food is cooked, and bills are paid. In a traditional setup, each step might wait for the previous one to finish.

Event-Driven Architecture (EDA) is different. It's like having many independent stations that react to things happening around them, without direct instructions.

At its core, an event is simply a signal that "something happened." It's a record of a state change or an action that occurred in a system.

• User clicks a button
• A file is uploaded
• A new order is placed
• A sensor detects motion

These are all examples of events!

Event-Driven Architecture involves three main components:

• Event Source: The system or service that generates an event (e.g., a user interface, a database change).
• Event: The data package describing what happened.
• Event Consumer/Processor: A service that listens for and reacts to specific events (e.g., an AWS Lambda function).

Events often travel through an Event Bus or Queue, which helps route them to the right consumers.

EDA offers powerful advantages for modern applications:

• Loose Coupling: Components don't directly "know" about each other, only about the events. This makes systems easier to update and maintain.
• Scalability: Event consumers can scale independently based on the event load.
• Responsiveness: Systems can react to changes in real-time, leading to a more dynamic user experience.
• Resilience: If one component fails, others can often continue processing events.

AWS Lambda is a perfect fit for Event-Driven Architecture. It acts as an event consumer or event processor.

Think of Lambda functions as tiny, specialized workers that are "asleep" until an event wakes them up. Once the event is processed, they go back to sleep.

A key concept with Lambda is that you don't manually "start" it in the traditional sense. Instead, other AWS services or custom applications publish events.

When an event matching a Lambda function's configuration occurs, Lambda automatically invokes (runs) that function. It's fully automated!

Events are typically structured data, often in JSON format. They contain details about what happened, when, and where.

Here's a simplified example of what an event might look like:

Let's trace a simple event flow:

1. A user adds an item to their shopping cart in your app (Event Source).
2. Your app publishes a "itemAddedToCart" Event.
3. An AWS Lambda function (Event Consumer) is configured to listen for this specific event.
4. The Lambda function automatically runs, perhaps to update inventory or send a personalized recommendation.

The app doesn't need to know how inventory is updated; it just publishes the event.

When Lambda is invoked, it passes the event data to your function. In Java, this data often comes as a Map or a custom object.

Try running this simple Java Lambda function. It prints the incoming event data:

Which of the following best describes the role of an AWS Lambda function in an Event-Driven Architecture?

Great job! You've learned the fundamentals of Event-Driven Architecture and how AWS Lambda fits into this powerful paradigm.

• Events are signals that something happened.
• EDA uses events for loosely coupled, scalable systems.
• Lambda functions are perfect event consumers, automatically invoked by events.

Next, we'll dive into specific AWS services that can trigger your Lambda functions!