Idempotency in APIs: you should be aware of this! 

🎯 Key Takeaways for quick navigation: 00:55 🔄 Item potency means the same operation produces the same result, crucial for consistent API behavior. 03:15 📝 Pay attention to the "post" and "patch" HTTP methods, as they can create or modify data, demanding careful handling of item potency. 04:41 🔑 The solution to item potency issues involves using an item potency key (X-Item-Poy-ID) to ensure requests aren't processed multiple times. 05:08 💾 Store the item potency key in a memory system, such as a database or cache, to manage consistent API behavior. 06:58 ✅ Attach the item potency key to your requests, preventing the same request from being processed twice. Made with HARPA AI

Can this be achieved with transaction? If first request fails in service just revert everything dont create burger and send error message to client

The best video explanation of this very critical issue high scale, highly reliable systems face. Subscribed!

Cool video ! How to make ajax request idempotent in a situation where user can create for example cards on the page ?

So it's equivalent to the concept of pure function?

Shouldn't you store the idempotency key in the database you're writing the order to so that it's transactional? Otherwise if the program crashes at any point between "executing" the order, and writing the idempotency key to storage (like redis), you'll still have the same problem

Do you have any video posted on Spring Rest API/ Microservices ? If yes then could you please share ?

Great video! Don't you think that storing this temp value on the client is not the most secure way? A client could easily clear cookie. If there is a mechanism in the backend that deals with duplicate requests, then this is a different story.

Can someone explain, when we should remove the idempotency key? I think we shouldn't save all the keys forever.

Would repeated calls of the function ‘makeRequest’ have different values for the idempotency key? If they do, then the api would process both of them, wouldn’t it?

Really interesting topic, been doing web development for 20 years and luckily never had anything like uber eats had! But the video was done really well and am looking forward to more from ya. Keep up the great work man

Nice video. I really like your examples and approach. Around 03:33 you discuss why POST and PATCH require idempotentcy but the other HTTP methods don't. There is a lot of information arguing the opposite which I found when I googled POST and PUT. At a glance the reasoning one way or the other seems to depend on the exact use case and how effectively the return status codes are managed. Perhaps you could add some discussion or commentary addressing the divergence of opinion.

how exactly the request will be retried with the same idempotency key?

6:37 what kind of cache? The automatic subtitle does not get it either... :)

Very clear explanation!!! Many thanks!!!

Extremely helpful! Thanks a lot! Subscribed!

Hey! nice explanation.. Which software you are using to demonstrate this..

Very helpful!! Thank you for this nice explanation!

I don't know if I agree with not needing to concern ourselves with idempotency for other methods. I'd say it depends on the API. There are some cases where DELETE for example should be idempotent, like when deleting an item from a doing cart (and setting the total cost for the remainder of the cart

When I was in my university, I ordered so many free food at the time of the glitch. Later on I was banned from uber eats and then uber and I just made a new uber account ande moved on. :) Great video by the way.

amazing video

Hey, Great video. Meanwhile, I'd love to know if tou use Nest js :)

I learned a lot 👌

It would be interesting to see the solution for backend

Great video!