AWS

More documents

Recommendations

Info

Amazon Simple Queue Service Developer Guide How Do I...? Welcome This is the Amazon Simple Queue Service Developer Guide. This section describes who should read this guide, how the guide is organized, and other resources related to the Amazon Simple Queue Service (Amazon SQS). Amazon SQS offers reliable and scalable hosted queues for storing messages as they travel between computers. By using Amazon SQS, you can move data between distributed components of your applications that perform different tasks without losing messages or requiring each component to be always available. How Do I...? How Do I? Learn if Amazon SQS is right for my use case Learn how Amazon SQS works Get Started Authenticate requests Understand responses Set a visibility timeout Share a queue Grant permissions to a queue Relevant Sections Amazon SQS detail page How SQS Queues Work (p. 4) Making API Requests (p. 12) Request Authentication (p. 17) Responses (p. 27) Visibility Timeout (p. 8) Shared Queues (p. 29) Using The Access Policy Language (p. 32) In addition, there is a glossary and an overview of our typographical conventions. Each section is written to stand on its own, so you should be able to look up the information you need and go back to work. However, you can also read through the major sections sequentially to get in-depth knowledge about Amazon SQS. API Version 2009-02-01 1
Amazon Simple Queue Service Developer Guide Overview of Amazon SQS Introduction to Amazon SQS Topics • Overview of Amazon SQS (p. 2) • Amazon SQS Features (p. 3) • Architectural Overview (p. 3) • How SQS Queues Work (p. 4) • <strong>AWS</strong> Identity and Access Management (p. 10) This introduction to Amazon SQS is intended to give you a detailed summary of this web service. After reading this section, you should have a good idea of what SQS offers and how it can fit in with your business. Overview of Amazon SQS Amazon SQS is a distributed queue system that enables web service applications to quickly and reliably queue messages that one component in the application generates to be consumed by another component. A queue is a temporary repository for messages that are awaiting processing. Using Amazon SQS, you can decouple the components of an application so they run independently, with Amazon SQS easing message management between components. Any component of a distributed application can store any type of data in a fail-safe queue. Any other component can then later receive the data programmatically using the SQS API. The queue acts as a buffer between the component producing and saving data, and the component receiving the data for processing. This means the queue resolves issues that arise if the producer is producing work faster than the consumer can process it, or if the producer or consumer are only intermittently connected to the network. SQS ensures delivery of each message at least once, and supports multiple readers and writers interacting with the same queue. A single queue can be used simultaneously by many distributed application components, with no need for those components to coordinate with each other to share the queue. Amazon SQS is engineered to always be available and deliver messages. One of the resulting tradeoffs is that SQS does not guarantee first in, first out delivery of messages. For many distributed applications, each message can stand on its own, and as long as all messages are delivered, the order is not important. API Version 2009-02-01 2
Page 1 and 2: Amazon Simple Queue Service Develop
Page 3: Amazon Simple Queue Service Develop
Page 55 and 56:
Amazon Simple Queue Service Develop
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
show all

AWS

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?