🧑 SQS FAQs

sqs-faqs.txt

SQS vs home grown message queue:
  > Hardware maintenance 
  > Sys admin costs
  > Complexity 
  > Requirement for redundant storage
  > SQS has no admin overhead and little configuration
  > Works on massive scale, processing billions of messages a day
  
SQS vs SNS
  > SNS allows applications to send time-critical messages to subscribers via push
  > SQS is a message queue used by distributed applications to exchange messages through a polling method. Decoupling send 
    and recieve components.
   
Message Ordering:
  > Done via FIFO queues to preserve order 
  > Standard queues provide loose-FIFO to attempt to preserve orders.
  
SQS guaranteed delivery:
  > Provide at least once delivery
  > FIFO - provide exactly-once processing * no duplicates in the queue *
  
SQS vs Kinesis:
  > SQS offers reliable, highly scalabed hosted queue. 
  > Kinesis streams allow real time processing of streaming big data and ability to read and replay records to multiple Kinesis 
  stream applications.
  
Pay for what you use
1 million requests per month with no charge

Messages are identified by a global unique ID

If message cant be processed a dead letter queue is used. Visibility timeouts can also be set to prevent other components recieving and processing a message after a time