Event-driven architectures

Event-driven architectures have grown in popularity because they help address some of the inherent challenges in building the complex systems commonly used in modern organizations. This approach promotes the use of microservices, which are small, specialized applications performing a narrow set of functions. A well-designed, Lambda-based application is compatible with the principles of microservice architectures.

Topics

• How Lambda fits into the event-driven paradigm
• The benefits of event-driven architectures
• Trade-offs of event-driven architectures
• Design principles
• Anti-patterns in Lambda-based applications
• Frequently asked questions

This chapter covers:

• The benefits of the event-driven paradigm and how it can improve throughput, scale and extensibility, while also reducing complexity and the overall amount of code in an application.

• How Lambda fits into the event-driven paradigm and how it interacts with other AWS services.

• The common trade-offs of using event-driven architectures, which include variable latency, eventual consistency, and handling asynchronous return values.

• Design principles that help you develop well-architected serverless applications.

• Anti-patterns to avoid, such as developing monoliths or implementing inefficient function patterns that cause unnecessary waiting.