AWS re:Invent 2016: Migrating Enterprise Messaging to the Cloud
Enterprises rely on messaging to integrate services and applications and to exchange information critical to running their business. However, managing and operating dedicated message-oriented middleware and underlying infrastructure creates costly overhead and can compromise reliability. This video presentation shows how enterprise architects and developers can improve scalability, availability, and operational efficiency by migrating on-premises messaging middleware to a managed cloud service using Amazon SQS. Capital One shares how they are using SQS to migrate several core banking applications to the cloud to ensure high availability and cost efficiency.

Trevor Dyck, Senior Product Manager, AWS Messaging
Quinn Easterbrook, Director Platform Engineering Capital One  


How the Amazon SQS FIFO API Works
(Jakub Wojciak, Trevor Dyck and Tim Bray, AWS, Nov 21, 2016)
"We have just introduced FIFO queues for Amazon SQS. These queues offer strictly ordered message delivery and exactly-once message processing. The FIFO API builds on the SQS API and adds new capabilities. This post explains the additions, how they work, and when to use them."

FIFO Queues with Exactly-Once Processing & Deduplication
(Jeff Barr, AWS, Nov 17, 2016)
"Today we are making SQS even more powerful and flexible with support for FIFO (first-in, first-out) queues. We are rolling out this new type of queue in two regions now, and plan to make it available in many others in early 2017. These queues are designed to guarantee that messages are processed exactly once, in the order that they are sent, and without duplicates. We expect that FIFO queues will be of particular value to our financial services and e-commerce customers, and to those who use messages to update database tables. Many of these customers have systems that depend on receiving messages in the order that they were sent."

Six questions cloud app developers should nail in an interview
(Stephen J. Bigelow, TechTarget, Feb. 29, 2016)
"Modern software development involves detailed integration tasks, and many cloud app developers require knowledge of back-end systems integration with platforms like NoSQL, Dynamo.db, Amazon Simple Queue Service and Microsoft Access."

Practical tips to ensure PCI DSS compliance when dealing with message queues
(Ben Rothke, CSO, Feb. 23, 2016)
"Amazon SQS has a robust feature set and is PCI certified and has a rich feature set."

Continuous Delivery and Effective Feature Flagging with LaunchDarkly
(John Kodumal, AWS Startups, Feb. 17, 2016)
"The biggest thing I’ve learned from using AWS at this scale is to put as much as possible in a persistent queue like SQS to be worked on later (so that processing incoming requests cannot be hampered by the queue getting backed up). At first, we used beanstalkd as the queue service, but as our load grew, beanstalkd could not keep up. We were persisting the raw events in the web application, and then just enqueueing a beanstalk job to correlate them after a delay. We switched to SQS for everything, and it is rock-solid."

Using Amazon SQS for scalable applications (Ofir Nachmani, TechTarget, Jan. 15, 2015)
"So, what does AWS SQS have that other queuing systems, such as Apache ActiveMQ, Rabbitmq or Redis, don't have?"