S14:Decoupling applications: SQS, SNS, Kinesis, Active MQ Flashcards
Your traffic will increase by 100x. You have already setup SQS standard queue. What should you do?
SQS scales automatically
You would like messages to be processed by SQS consumers only after 5 minutes of being published to SQS. What should you do?
Increase the DelaySeconds parameters
Your consumers poll 10 messages at a time and finish processing them in 1 minute. You notice that your messages are processed twice, as other consumers also receive the messages. What should you do?
Increase the VisibilityTimeout
Usando alguna catergoria de SQS: You’d like your messages to be processed exactly once and in order. Which do you need?
SQS FIFO queue.
the order of operations and events is critical, or where duplicates can’t be tolerated.
Provide exactly-once processing but have a limited number of transactions per second
You’d like to send a message to 3 different applications all using SQS. You should
Use SNS + SQS Fan-Out pattern
Que nos provee cada Shard
Each shard allows for 1MB/s incoming and 2MB/s outgoing of data
Que podriamos usar si la user data no esta siendo ordenada y esta siendo enviada a diferentes shards
We can use a partition key that represents the identity of the user
We’d like to perform real time analytics on streams of data. The most appropriate product will be…
Kinesis
We’d like for our big data to be loaded near real time to S3 or Redshift. We’d like to convert the data along the way. What should we use?
Kinesis Streams + Firehose
You want to send email notifications to your users. You should use
SNS
Has that feature by default
You have many microservices running on-premise and they currently communicate using a message broker that supports the MQTT protocol. You would like to migrate these applications and the message broker to the cloud without changing the application logic. Which technology allows you to get a managed message broker that supports the MQTT protocol?
Amazon MQ
