@dheereshsingh6415

i got interviewed today and DLT been asked, now my concept is absolutely clear, thanks for this amazing stuff ๐Ÿ˜๐Ÿ˜

@yogeshchaudhari9971

Exceptional....eas never knowing about DLT ...... really made my day with feeling that i learned something new today....i anyways always keep watching many of ur posted vidoes.... thanks for ur efforts for sharing ur knowledge

@vino7tech

Another real time video from you sir. Thank so much sir  for your hard works

@augustineanosike741

Great work , exactly what i have been looking for , thanks a lot for the hard work in bringing this tutorial .

@AvinashKumar-d1i1p

This guy literally explains everything in very simple way ๐Ÿ‘

@narmada9190

I am not aware of this. Thank you soo much for all your videos.

@GunelMammadova93

Thanks a lot for these amazing tutorials! I learned a lot from your videos.

@EkundayoBlessing

Thank you so much for your great work. I completed this series!

@gopisambasivarao5282

Appreciate your efforts Basant. God bless youโค๐Ÿ˜Ševery week waiting for new updatesโ€ฆ

@Mronline-xyz

Excellent content... As always, thanks alot Sir.. ,๐Ÿ‘๐Ÿป

@phanimc11211

Thanks a lot on good work ! As usual  this video is always informative and practical

@suvarnabg1056

thank you sir for your clear explanation. ..

@satyabratasahoo967

Another scenario is: why not to wait for the external service to wake up so that we can resume the processing.  This way we can avoid one drawback of the earlier approach.  which is as follow:
for one entity we got error and we pushed it to dlt. but we got another message for the same entity and this was processed successfully.  now when the dlt msgs will be processed, this will update the entity as per previous data which will create data inconsistency.  

Waiting for the service to wake up will ensure two things.
1. safe guard the chronology of the events
2. no unnecessary consumption and retry and then publishing to dlt.  

This is my observation.  I would like to hear from you on this. Thank you sir.

@KuchNahiBasAiseHi

Great work sir. Thanks again

@santhoshpola2182

Hi, Thanks for detailed videos on Kafka. Can you also make a session on Kafka Transaction management?

@m4riders

Sir ji ki jai ho ๐Ÿ™

@sahilpatil1111

Hello, please make video on Spring Boot Hexagonal Architecture, lot of company's are using as modern development, i struggle a lot still don't understand entire structure.

@CenturionDobrius

Thanks a lot on good work !

@NagaMahesh-y1u

Hello. Thank you for your clear explanation. When i tired in my local machine with the Retry and DLT mentioned configurations with the spring Boot 3.3.2 + kafka(In built version 3.7.1)  version the excepted output is not working. Can you please help me on that.

@manindersingh6371

Hi Brother: Nice video! The way you explained everything is exceptional. Keep up the great work! However, I encountered an issue where I couldn't send the message to the DLQ until I threw an error in the catch block. The existing blocking didn't trigger it, so it didn't work for me. I'm sharing this in case it helps someone with a similar problem. Also, please consider using docker-compose for Kafka in future videos.


Code I changed:
Instead of "e.printstackTrace" in catch block, I used "throw e";