In this chapter, we discussed the details of the Messaging Pattern and walked through a complete example using AWS SQS as a message broker. The example application comprised a Lambda function as the data producer, SQS as the message broker, and a Lambda function as the data consumer, which ultimately stored results in DynamoDB. We also discussed the difference between queues and streaming systems and reviewed their merits and use cases when one may be preferable over another. I also explained alternative architectures and implementations of the Messaging Pattern with specific problems and examples given for context.
At this point, readers should have a good understanding of how to break apart data-heavy serverless applications using queuing systems to provide scalability, fault tolerance, and reliability. I presented alternative architectures, which should give readers some insight into how they can structure their applications for improved decoupling and performance.
In the following...