Hi, thank you for sharing very interesting topic, but I disagree with the method of CodeCrafters of recreate something that already exist. For me Is Better tò have a timed coding contest with real world project in order to improve and learn new skills.
Very useful. Thanks for this!
Glad to help. Thanks for reading!
Great article. Nicely illustrated! Thank you, Raúl.
Thanks, Rafa!
It's useful info,
Glad to help. Thanks!
I use to combined retry and DLQ, I appreciate your show up when retry or not retry. Seems obvious but worth to noticed!
Retry and DLQ are a good combo for so many cases that they are hard to ignore.
Thanks, Romain.
Great article with underrated topic, Raul!
Thanks, Heru!
fantastic article, thanks a lot, Raul
Thanks, Neo!
Enjoyed reading it. Great article Raul!
Also, thanks for the mention.
Glad you liked it, Ashish.
Thanks!
An excellent breakdown about and underrated topic.
And thanks for the mention my friend.
Keep those articles coming, my friend.
Thanks!
Working with payments is crucial. This was one of the reasons I joined such a company last year.
Great article, Raul!
Excellent explanation Raul.
I really liked the point about identifying transient errors vs permanent failures. An intelligent payment system should know when to stop.
Thanks for the mention as well!
Hi, thank you for sharing very interesting topic, but I disagree with the method of CodeCrafters of recreate something that already exist. For me Is Better tò have a timed coding contest with real world project in order to improve and learn new skills.
It's all good; everybody learns in different ways.
The idea of reconstructing these projects is to understand how they were built, the scale of the problems they solved, and the trade-offs they made.