AWS SQS Overview For Beginners

[@sureshbabu8794]

Your AWS videos are far better than paid courses. Very clear explanation. Thank You!

[@jude3926]

You really don't understand how this video just saved me stress. Thank you. Love the visual explanations and the details such as common use cases, etc... keep it up

[@BeABetterDev]

Thanks so much Jude and glad you found it helpful!

[@lanatimmo3686]

I was always scared of the SQS/SNS, and could never really understood them😅. Thank to your videos I do now! Very grateful for your great content and very neat and clear explanation, thank you a lot!☺

[@miguelviamonte8041]

Men! I can't appreciate all your videos enough. They had guided me on from zero to "hero" on my serverless journey in my new job (I started 6 months ago). I have a whole notification system for AWS Backup using SNS / SQS / Lambda running right now!

[@marklautman4853]

Superb. The clearest description of SQS that I've come across.

[@rajendrawarrier7274]

Elegant way of explaining - simple and crisp - no fancy show business. Great job!

[@kino-xw4xg]

This video has been extremely helpful with my studies for SAA, just wanted to thank you so much for this

[@BeABetterDev]

Glad it was helpful!

[@jamolkhonumarov5188]

one of the best explanation out there and it's free. Good job man

[@BeABetterDev]

Glad you liked it!

[@himanshuagrawal2014]

Thanks a TON for such a tremendous , easy to digest video. Quiet explanatory at the same time. LOVED your pace of teaching and explaining the concepts. Stay Blessed Brother !

[@BeABetterDev]

Glad the video helped and thank you so much for the kind words!

[@16beat41]

This is the best tutorial video ive seen for SQS

[@islamtoghuj]

I think this is the best channel to get a great overview of AWS.

[@markcaro4419]

Excellent introduction to SQS!

[@BeABetterDev]

Thanks so much Mark!

[@anaghakr]

Excellent introduction to SQS! Thank you!

[@vijji8942]

Thanks for sharing comprehensive understanding of SNS. Appreciate your efforts!!

[@Room3102]

Another clear, straightforward, awesome video!! Thanks, man!!

[@BeABetterDev]

You're very welcome Clerton!

[@ulricha.abiguime7918]

thanks for putting all this information short for us, lazy ones

[@Hiroki-Takahashi]

Excellent video as always!

[@pythonbrothersandfamily]

PURE GOLD. Thanks a loooooot Be A Better Dev is my shepherd; I shall not want. He maketh me to lie down in green pastures: he leadeth me beside the still waters. He restoreth my soul: he leadeth me in the paths of righteousness for his name's sake.

[@bouzie8000]

Thoroughly appreciate this video. You have no idea

[@ktapython600]

Hey Better dev, Just wanted to thank you for the tremendous time you spend on putting all these materials together and then compiling them for the great and educative videos you produce for all. You are a true leader, a role model, and a trendsetter for many. Keep up the good work because you are impacting lives worldwide, and I want to thank you for your selfless sacrifice to the human race. Jah, Rastafari!!!

[@chris0628]

Awesome content…saved me hours of google and reading through documentation 👌🏽

[@BeABetterDev]

Glad it helped!

[@mayankparmar8155]

Hi @BeABetterDev , 1). Can SQS accept an Event Published from a System (example : Salesforce - Events) ? 2). What is the count of messages that an SQS can accept from an external System (i.e, Published Message Count from System -> Amazon_SQS ) ? 3). Can SQS accept Bulk Messages / Events ? Please let me know. Great video, Clarified in a single go.

[@andrewmcburney4425]

You're a great teacher - thank you for the video

[@BeABetterDev]

Thanks so much Andrew! Glad you enjoyed :)

[@alizadasaleh2291]

Very Clear Explanation!

[@np8688]

Simply explained, thank you ! Keep up ;)

[@BeABetterDev]

You're welcome!

[@arrecky]

great, thanks for explaining it in a really simple way

[@islamh6042]

Great illustration, thanks for your efforts. Much appreciated!

[@amineelmhamdi3576]

Thanks

[@BeABetterDev]

Thank you so much for your generosity!!!

[@eiderarango5863]

Thanks bro, nice video. Keep it up.

[@BeABetterDev]

You're very welcome and thank you!

[@r_mani41]

U R A WONDER

[@samikshasharma3544]

Amazing video

[@triminhtran2470]

Thank you so much

[@ahmadfahmi5129]

Thank you for this fancy explanation

[@as180697]

Thanks!

[@sergiojuradolozano]

very well explained. Thanks!

[@milanvarma4120]

Amazing tutorial loved it

[@et4493]

Top notch content man. Thanks!

[@StraightCoding]

Very Good explanation, i like it👌

[@Radekk225]

Great explanation thanks!

[@chessmaster856]

Sqs has a limit of 10 messages and 256kb message size. That sounds something very obsolete technology not really modern high performance

[@sreejithsreedhar05]

Indeed the video is very informative ,Thanks for sharing . I have a small doubt ,similar to query parameters in API how we incrementally poll messages from SQS queue. I would need to poll messages based on a particular timestamp.

[@malikmubashar5040]

thank you so much for this

[@AbdelhameedG]

Thank you

[@BeABetterDev]

You're welcome!

[@totsubo2000]

Great video. What are the downsides/tradeoffs of using SQS vs. SNS? In my mind SNS can do everything SQS does and more (i.e. supports multiple subscribers). Also you mention that the consumer sets the consumption rate. How would that work with something like having a Lambda as the consumer? I'd imagine Lambda would spin up as many instances are required to process as many SQS messages as quickly as possible.

[@BeABetterDev]

Hi Jean, I have a video that compares the two check out the link below. kzbin.info/www/bejne/o4nOYYCEn9GCbaM

[@stayingaliveable]

thank you for this video!

[@saragasmichalis2177]

Great video !

[@BeABetterDev]

Glad you enjoyed it!

[@edwinmarrima6476]

Perfect explanation

[@BeABetterDev]

Glad it was helpful!

[@SilvanaV-r3c]

You are AMAZING!!! I've not had a single video explain anything as clearly as you do. Please keep doing what you're doing and MORE of it, because you are a natural teacher of the best kind.

[@Erica-up2xm]

Great Explanation. Have a quick question. I have multiple queues where the poller should be fetching the messages from all of them based on some priority. And the priority would be like this - for example 1st queue having only 2 messages, 2nd queue having 100 messages and 3rd queue having 1000 messages then I want the poller to initially poll the queue which has less number of messages i.e here the poller should initially poll 1st queue then the 2nd and then the 3rd. How can this be achieved.

[@rishiraj2548]

Gratitude

[@abdelhadidjafer7004]

man ! i wish i work under you as my senior !

[@BeABetterDev]

One day ! :)

[@abdelhadidjafer7004]

@@BeABetterDev thx

[@BR-lx7py]

What happens in a FIFO if a consumer could not correctly handle a message and it is requeued? Does it block other messages being processed, since it's a FIFO?

[@BeABetterDev]

Hi B R, great question. I couldn't find any direct answer to this on the AWS documentation but here is something insightful. From here, under "FIFO queues": docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-dead-letter-queues.html "FIFO queues provide exactly-once processing by consuming messages in sequence from a message group. Thus, although the consumer can continue to retrieve ordered messages from another message group, the first message group remains unavailable until the message blocking the queue is processed successfully." I feel like based on this it probably blocks the queue from processing messages in the same message group. However to know for sure its probably worth a quick experiment.

[@BR-lx7py]

@@BeABetterDev I played around with it and FIFO-s are blocking. Inserted 3 messages into a FIFO with send-message, then the first receive-message returned the first inserted one, but then calling receive-message again didn't return anything. Had to do a delete-message with the receipthadle of the first message to get the second one inserted. You'd better handle your exceptions in the code that processes the messages.

[@foobarbecue]

25:24 I guess Clodudwatch is for monitoring failures to launch (duds)

[@mikami5799]

Why sending messages to Queue is an anti-pattern?

[@the80scyborgninja39]

Would this be ideal for returning a dictionary from a lambda as a message to be consumed by other lambdas?

[@Nabilliban14]

Thanks for this great overview! Quick question, as part of the "at least once delivery" that standard SQS provide, can I assume that duplicates will have the same messageID? Also, even though it is "at least once delivery", I can assume that there won't be two versions of the same message in a queue at the same time, thus respecting the visiblity timeout you mentioned at 11:20, right?

[@surajthallapalli4227]

Legend !!

[@tomasesber6056]

Nice. My question is: what are the drawbacks of this continual "polling" being done by Service B in your minute 17:30 example? Suppose your service A does not send messages to Service B for months on end, is this "polling" costing anything (i.e., computational cost in terms of site performance, AWS fees)?

[@tomasesber6056]

Should have finished the video before asking... it seems like Long Polling avoids the need to continually poll for messages. Still curious about the drawbacks of this, though.

[@BijanHoomand]

Great video. Quick question: when you mention cross account patterns, do they also support cross partition data transfer? For example if I have an AWS account in China and another in USE1, can I publish from my SNS queue in China into my SQS queue in USE1?

[@BeABetterDev]

Hi Bijan, Cross region sns to sqs works for all cases except involving the china region. I found this post on the topic if you're interested: stackoverflow.com/questions/69061869/is-it-possible-to-publish-sns-messages-from-global-aws-account-to-sqs-queues-in Hope this helps

[@BijanHoomand]

@@BeABetterDev LOL, thanks heaps for checking it out. Yeah, unfortunately it seems it is not possible. I am investigating if there is a way to make that happen; IAM seems to be out of the picture; I am thinking of using temporary security credentials with SQS: docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-using-temporary-security-credentials.html ; will keep you posted if I could somehow pull it off

[@potatoman2602]

Thanks for all these videos. Do you have a video on local dev environment with aws - I couldn't find one? How do you approach this? Do you test against another dev aws environment or do you spin up everything locally with mocked/faked services like localstack?

[@BeABetterDev]

Hi Potato Man! Check out this video on my setup: kzbin.info/www/bejne/eXimn2OYaauCnNU I haven't made one for IDE / plugins but if you think it would be useful I can make one. Cheers

[@emirdagdelen6465]

fucking legend.

[@abdulrameez151]

Can we do an interview, need you input for my university project

[@abdulrameez151]

Please brother

[@mrrishiraj88]

👍

[@uz16]

What if the Queue goes down lol

[@Brand73]

Good, you mispronounce the word 'process' in all of your videos. It's a little distracting but the content is excellent👍

[@SemenAlexndrovich]

Your videos are amazing! Thank you so much!

[@BeABetterDev]

You're very welcome Semyon!

[@bishnuprasadmishra1733]

Excellent introduction to SQS! Thank You!

[@munteanionut3993]

Lovely AWS tutorials. Kudos to you and I hope you will keep it going! Could you please better explain the beginning? 00:00:42.160 in the past when two services had to 00:00:44.399 communicate with one another one service 00:00:46.559 would perform an api call to inform the 00:00:48.960 other service that something changed or 00:00:51.039 some kind of event occurred on its side 00:00:53.680 now using sqs this contract has changed 00:00:57.039 instead the producing service of the 00:00:59.359 event or the notification can 00:01:01.359 asynchronously notify the consumer that 00:01:04.080 something changed in its system I do not understand what you were trying to imply.. by how I interpret it & how the above text is phrased; you say - in the past: one service had to inform the other something changed on its end through an API call - now: the contract changed, id: the service in which something changed (same as above till now) can asynchronously notify the consumer that something changed in its system... how do the above differ? did you mean API calls in the past were always "blocking" instead of "async"? is this what you meant? I do not follow, sorry..

[@lholhofox]

Thanks for this video!! Keep it up!!

[@m.e10150]

Thank you very much