AWS Simple Notification Service Complete Theory-Hindi/urdu | Lec-96 | AWS SNS Features | SNS vs SQS
ฝัง
- เผยแพร่เมื่อ 10 เม.ย. 2020
- Lec-96 AWS SNS Theory lecture.in this lecture,i am explaining all the features,pricing and components of SNS.
Now you can donate us via Paypal and Google Pay:
Paypal id - www.paypal.me/technicalguftgu
Google Pay UPI- bhupinderccs@okaxis
Do subscribe to TECHNICAL GUFTGU channel and Press Bell icon & get regular updates on videos, DIRECT LINK TO CHANNEL : / technicalguftgu
Here are direct links of My All the Playlist: MUST CHECK
IPv6 Complete Tutorial for beginners Link : • IP Version 6 Tutorials...
Microsoft Azure Tutorial for beginners in Hindi/Urdu AZ-103 and AZ-900 LINK : • Microsoft Azure Tutori...
Cloud computing tutorials For beginners Link : • Cloud Computing Tutori...
AWS Solution Architect-Associate complete Tutorials Link : • AWS Solution Architect...
CCNA Complete Tutorials /Computer Networking Link : • CCNA Full course in Hi...
This is the best channel for AWS Tutorials, Microsoft Azure tutorials, 2G,3G, LTE, CCNA, Cloud computing and for others topics related to cloud and computer networking. Technical Guftgu is the only platform, which provides you entire training on white board, so that you feels that, you are taking real time training.
Bhupinder Rajput Sir is having 8 Years of Experience in the field of technical trainings in entire india.
NOTE : If you would like to organise Bhupinder Rajput Sir workshop in your College or University, write mail to us.
For More Information:
Please write us at : technicalguftgu99@gmail.com
Connect with us on facebook page-Technical Guftgu for his upcoming 5 Days workshops on cloud in india and Nepal. If you would like to donate and give support to our Channel, write mail to us.
Thanks For giving Your Valuable time.
Regards,
Technical Guftgu Team - วิทยาศาสตร์และเทคโนโลยี
![แฉ [2/4] 12 ก.ค. 67 เจ้าของไวรัลดังในโซเชียล 'ลิลลี่ เหงียน' ฝันอยากเข้าวงการ โดนหลอกสารพัด | GMM25](http://i.ytimg.com/vi/7zntQK2U8-8/mqdefault.jpg)
DLQ : incase the messages are not processed by servers(3 times consecutively), they will be kept in DLQ so that developers can look into the issue afterwards.
once a message is done with its visibility timeout, it moves the message to DLQ , so that it can be treated later either automatically(i hope could implement a service) or manually by the team to check errors for the reason it was in DLQ.
Thanks for the tutorial . Amazing one as usual.
Thanks,
Kya bolu sir apke jaise teachers k wajah se bahut saare students life me kuch ban sakte hain ...aapki saari wishes Puri ho sir ...love u frm Karnataka bidar
aap ki lecture delivery Maasha Allah....
Sri Guredev ke charno me shastang pranam.......10+ yrs Exp Guy from BLR, i am learning alot from your lectures which will help me in my upcomming interviews.
Great, mene dono ki service use ki h production par but ab bol skta hu now clear all doubts
Thanks👍👍
When sqs queue object not fully processed with 3 times than it will remove from the queue and add into DLQ.
sir your are best teacher and your videos maters everything for me🙏
One of the finest tutorial on AWS available on web including PAID platforms. I am your FAN of style of explanation in a simple manner. I remember I subscribed your channel when I saw your Networking concept. Now I am following your AWS series. Please brief the AWS Kinesis and Live streaming with AWS in near future.... THANKS FOR YOUR AMAZING VIDEO LECTURES in a very simple way....
Amazing training watching from US.I learnt a lot about computing which are not easy to learn from other online videos.God bless you.
Iam from Hyderabad Telangana sir u r excellent teacher sir , really u explain in detail
Thank you. Was waiting for this from many days. Aap hi ho joh details mein explain karoge
Sir, you are doing great job by sharing your knowledge. Thanku
We eagerly wait for ur videos.. excellent.. Thank u so much sir..
Thank you Sir..!! for providing wonderful lectures....
DeadLetterQueue: When servers are unable to process a particular queue msg for atleast 3 times then it creates dead letter queue stating some code to make understand the developers team to debug...
very simple and easy way explained. Superb one
Superb just watching ..... ...
Very knowledgeable and interesting lecture sir, Thank you
Thankyou Sirji...
Congratulations on 200k sir!!! We respect you!
Thank u sir for detailed explanation ❤
Very beautifully expalined..thx for great lecture...dead letter contains those unprocessed mesages which requires further analysis manually...
Great explanation sir 🙏🙏
Thank You Very Much Sir..........................................
Awesome video
Thank you sir.
Nice lecture as usual
thank you so much.
Thanks sir..nice session sir
when SQS msges failed to process three time they moved to DLQ, and then developer and technical team will take a look of that problem
Bbhuhxbq bc,vjb qyucc, hoow bcs. Ed DC eve
Was. Sc
:sh!
Pa
I enjoyed your AWS Associate Series. Please create AWS big analytics series.
Thank you so much sir
Thank you Sir..!!
Great work done by you. Really liked your work. Please make video on eventbridge and comparison between SNS vs Eventbridge. Thanks.
Thanks sir..
thanx sir
Super sir..
dead letter queue basically wo msg hoty hen jo servers process nahi kr paty jisko bad me developers handle krty hen ....
love from Pakistan sir...
When the message has failed to processed move to dead letter queue. Thanks a lot for this lecture.
A dead letter queue is a queue that other queues can target for messages that can't be processed successfully. You can isolate these messages in the dead letter queue to determine why their processing did not succeed.
ThnQ sir......
There may be lots of message in either standard or FIFO queue. Those messages are to be further proceeded as per the specified resource. For an example, a bucket with technical guftgu is created. The video is to be stored in a bucket. If that bucket is deleted then the video is unable to be uploaded. So the message will be strike repeatedly to sent for storing as mentioned config. Finally if the message is unsuccessful to function as stated then it will be sent to dead letter queue.
So, dead letter queue is a message stored in a queue where the details will be available with reason. It is basically handling the failure message that went through SQS/FIFO queue.
Thank you so much sir 🙏. Please upload lemda video also
Nice video
Sir ap sqs lab ko thoda detail me bata de to maza aajayenga..
Recent sqs lab bht easy thi ,thoda advance level par raha to bht zyada helpful rahenga ..
Thanks for everything
tYSM SIR JI
Thanks Sir , pls include Kinesis firehouse
Sir please continue AWS series further .🙏🙏🙏🙏
Nice
today is my interview hope it gets well
Thank You Sirji
whenever SQS failed to process the queue message, that message is going to DLQ(Dead letter queue).
Dead Letter Queue: When the file is unable to process, an API call is made to notify the IT Department to look into the matter. It's used with Standard queue because in FIFO queue the requests will be arranged in sequence which is not helpful for us.
dead letter queue is a section where request msgs are stored. The msgs which are rejected 3 times in short polling, after it been send to 1 server then visibility timeout for 30 or more secs, if the server that more time then visibility timeout is extended but if the server fails to process the msg is unlocked in queue for other servers to read and if this fails happens more than 3 times the the msg is stored in dlq in s3 where then its resolved manually by devlopers.
Sir,
We are waiting for your Microsoft Azure Classes .&
We have alreday completed your azure all classes.
Sir When you Upload Next class of Azure ???
Sir again request you to please make videos on docker container and kubernets, lambda function.
DLQ is a part of SQS where messages are being stored which was not able to be processed by servers for 3 consecutive times. Later developers have a look on it and sort out the problem and again make it ready to be processed by servers.
Thank You Sir for detailed tutorial ...
DLQ: It is set of messages which server were unable to process. Server tried 3 times and still unable to decode/process the message due to any failure, that messages goes to DLQ and those messages are later investigate manually.
Dead letter queue is a function used is AWS sqs, wherein the message is sent after 3 unsuccessful attempts of processing
hello sir
nice tutorial.
sir also make video for difference between aws SES vs aws SNS.
which was better and why?
A dead letter queue is a place where unprocessed data store, then the technical team check why these data could not be processed and takes appropriate action to fix the error.
You worth Love
Hii Form Canada, Your tutorials are awesome. Keep up the good work. Especially, your shayari is very nice. Please let me know if you are on Linkedin or not. I would love to follow you. Thanks very much again.
Sir mujhe maloom he en sawaloo ka aap ki es video se koi taulaq nahi he leqen me ne socha k jo sab se latest video he ap uske comments parhe ge tou inshallah ap jawab bhi dege. Sir aur ek suggestion he k ap Q n A ka session bhi start karde . Es ka ek faida ye hoga k videos tou ap kisi particular topic par banate he magar es me student ap se networking aur computer k hawale se koi bhi sawal poch sake ga aur ap inshallah us ka mutmaen jawab de pae ge aur ye ap k channel ko ek unique look bhi dega jes se meri dua he k ap k subscriber mazeed badhe ge.INSHALLAH.
Dead letter queue: it is phenomena when a message is not able to processed by any server in consecutive manner then it is sent to Dead letter queue.
When servers fails to process the sqs messages thrice, it then pass the message from that queue to dead letter queue so that the failure part could be resolved by the dev team.. in the other words dead letter queue are for technical teams to resolve the failed messages.
Please keep a background music while doing shero sayari.. It sets the right mood.
Jab bhi kbhie Aapka visibility timing(X or X+Y)[first case : visibility time=X ; second case: visibility time=X + Y(extra time added) khatm ho jaaye iska mtlb hai ki iska process Nahi hua aur yeh problematic hai ..issliye dead queue(jao maro queue) main daal diya jata hai ..phir developer(doctor) inko pakad k thikh krte hai.
Bhupinder Bhai aap Aws Kinesis pe lecture bnao plz...
Hi Sir, It would be better if you make question and answer with explanation for solution architecture associate exam.
Waiting for lecture on SWF
A dead letter queue is an Amazon SQS queue that an Amazon SNS subscription can target for messages that can't be delivered to subscribers successfully. Messages that can't be delivered due to client errors or server errors are held in the dead-letter queue for further analysis or reprocessing.
20k view and only 970 like .. plz support him hes best in his work.
DLQ handles the failed messages in SQS. In SQS, if a message request is failed thrice it is stored in DLQ which is later handled to identify and manage the failures.
Hi Sir...I hope you are doing well...will you upload the video of Elastic Beanstalk topic...?
Very helpful video.
Dead letter que services is a when servers try to process message . But it's unable to process by servers and failed more than 3 times. So message move to dead letter que.
Dead letter queue used to store messages which are continuously failing so that later we can have a look at that messages to debug or resolve.
DLQ means whenever message are not able to go for further process. this is go for 3 times afterwards the messages go to Dead letter queue.so respective authority take action on this for further processing.
Dead Letter Queue contains the messages that are not processed in three consecutive attempts by the server after pooling from SQS.
Please make videos on AmaZon Connect with outbound
Dead letter queue is place where messages which are failed (3 times) threshold particular times are stored
itne ache se apne apne padha diya h ab toh dimag se nikalna not possbile
a dead letter queue is queue where unprocessed message are delivered
three consecutive failed message processing by multiple server in standard queue in SQS , is considered as dead letter queue, and these message will transfer to dedicated team to check what is wrong with those message which was not processed by the servers.
Dead Letter Queue: When a message has failed three times then it is moved to Dead Letter Queue for analysis by technical team.
Dead letter Queue := If we send a message for polling and some how the message in not filter or processed by server then it will back in queue,this process is continue after some time the message will store in dead letter queue.
If any message fails 3 time than it goes dead later queue...
Thanks sir for AWS detailed in Utube
When server fails to process sqs message for 3 times then at that time the message is removed from queue that process is called dead letter queue
Watched on 2/10/2022
in dead letter queue if the message in the queue is not get processed by the 3 or 'n' no of the servers than that message is referred to the dead latter queue and that message was manually read by the developer or the programmers to process that query
SES lecture needed
dead letter is consecutive fail process through server
When SqS message is failed to get processed as per set limit, It goes to DLQ for developers to see and troubleshoot.
sir can u do videos on packer and terraform
Once visibility timeout over, messages moved to DLQ which later on tare care by support team.
Dead Letter Queue: It is the process when a request hasn't been processed by any servers due to some reasons, then SQS send this request to the Dead Letter Queue. Now develope/backend team will do the root analysis why it hasn't bee processed and get the things done.
Please correct me if I am wrong anywhere.
When a request is pulled by application and application is not able to process the request within visiblity timeout then that request is returned back to SQS and same request is pulled by another available application. In case the request doesn't get process within the set of threshold then request will be sent to dead letter queue which will be debugged and processed manually.
deadLetterQueue : When any SQS has been failed 3 times then it will store msg in SQS and its can be proceeded manually.
When servers trying to process the request but that request is failing and due to that it will goes into dead letter queue so that other messages can be processed accordingly
When msg in Q reaches maximum visibility time but fails to process those msg moves to DLQ for futher analysis.
When a message is pulled by a server from the queue and its visibility timeout also gets over but still its unprocessed by the server so again pushes its back to the queue and from here some other server takes it , the process repeats and if the same message is failed for three times from getting processed by different servers than it is used to dead letter queue (DLQ) from where the developer or the AWS team checks and find out the cause behind it .
If server can not pull the messages continuously 3 times from queue then it will send in dead letter queue which means these are the messages that are not processed by server. In DLQ, team will manually check the issues, why they can't be processed.
the msges which are not processed by servers after its given time it will be send to DLQ.
In sqs if pull service fail three time api then element will be enter in del queue and operate by the developer.