This is the best explanation I've ever seen for SNS vs SQS. Thank you for your time in creating this content. Very helpful !
@vardaanaashish6753
Жыл бұрын
Fantastic explanation Gabriel! Thank you for sharing 🙏
@ivan.romaniv
3 жыл бұрын
That's really good explanation. Thank you!
@Gabzim
3 жыл бұрын
Thank you for taking the time to leave a comment.
@augusto2581
2 жыл бұрын
Gabriel, congratulations and thank you very much for the video. It helped me a lot!
@Gabzim
2 жыл бұрын
Hey thanks! Been struggling to make KZitem videos lately and these comments are giving me the push I need
@TheVaradasantosh
3 жыл бұрын
Thanks much for sharing Knowledge & Thought process . your Content is very helpful.
@Gabzim
3 жыл бұрын
Thanks, comments like this keep me going
@evanhl4878
2 жыл бұрын
Hey Gabriel! Thanks again for the awesome videos. Question regarding using SNS and SQS together: Let's say I have a system where I batch data in a queue to be processed every X amount of hours. Instead of having a "queue" per service, would it be possible to put these batches on SQS, then have SNS (or some lambda that connects to SNS) pull these batches from the queue to then notify my service that a batch is ready to be processed?
@Gabzim
2 жыл бұрын
I haven't seen SQS and SNS used this way, it's usually the reverse, an SNS topic pushing to multiple SQS queues. The biggest reason for this is that SQS is meant for transaction workloads and if you were to use it to fire an SNS message, you'd be giving that up. You're better of posting a message to SNS saying a batch is ready then each service pulls from the SQS queue assigned to it (one service can have multiple instances).
Пікірлер: 10