![]() Now that SQS is an event source to Lambda, all that heavy lifting of managing message polling and deleting has been offloaded to the Lambda service, which is now your SQS consumer. The source queue is NOT triggering your Lambda function. It’s important to know that nothing has really changed with SQS since announcing SQS as an event source. Think of it like building your own webhook for an API. It was a hacked way of event-driven development. You even had to write logic to know when to back off polling and know when to delete a message or let it go back into the queue. Either way, it was a service you, as a developer, had to build, monitor, scale, and maintain. This could be done with short polling or long polling. ![]() Prior to SQS becoming an event source to Lambda in late June 2018, developers needed to create a service/client to poll an SQS queue for new messages (also known as an SQS consumer). ![]() So Why All the Hype and What Has changed With SQS? Simple Queue Service (SQS) is scalable, low latency, offers unlimited throughput, at-least-once-delivery, batching, server-side encryption, serverless messaging service.Īll that capability existed for years, long before SQS became an event source. After you are up and running, follow along for a deeper dive into this serverless event-driven architecture. In this article, I’ll go over the details of SQS as an event source, the Lambda integration, and then we’ll quickly build this architecture using pre-built AWS CloudFormation templates to provision the backend resources. All the “consuming of an SQS queue” is managed for you and we’ll explore what role each service is playing as part of this new architecture. What has changed is the managed backend resources for consuming content sent to the queue. Sending these messages to SQS hasn’t changed SQS is still low latency and batch capable, has very high throughput, and is an affordable alternative to using other storage options and no data store schema or tables to setup. I can now send all my event-based messages, logs, and analytics from my iOS application directly to an SQS queue. ![]() SQS as an event source to Lambda is a game changer. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |