Summary
Keywords
Full Transcript
Event-driven architectures need a reliable way of analysing missed or errorneous messages that have been lost along the way. A Dead-Letter Queue is one of the most popular methods for that. Let's learn how message queues can fail, how they can produce deal-letter messages, and how developers can later analyse them using the RabbitMQ UI or similar. ======⚡⚡⚡====== Consider becoming a member of the channel by joining me ❤️ https://www.youtube.com/channel/UCqAL_b-jUOTPjrTSNl2SNaQ/join ☕ Buy me a coffee: https://www.buymeacoffee.com/softwaredeveloperdiaries 🙌 Become my Patreon and get exclusive perks: https://patreon.com/softdevdiaries 💼 Follow me on LinkedIn and drop me a message if you'd like: https://www.linkedin.com/in/gadirovgs/ 💻 Also, let's connect on GitHub: https://github.com/gusgad 📚 Resources: https://aws.amazon.com/what-is/dead-letter-queue/ Code: https://github.com/gusgad/youtube-tutorials/tree/dead-letter-queue And don't forget to subscribe for more videos like this 😊
