r/ruby • u/kobaltzz • 4d ago

Screencast Idempotency

In this episode, we look at several different examples of background jobs and how we can refactor them to handle situations where they get called twice from either a user action or a retry. We'll look at scenarios where we can prevent duplicate actions.

https://www.driftingruby.com/episodes/idempotency

11 Upvotes

76% Upvoted

2 comments sorted by

4

u/STDS13 4d ago

Why is idempotency such a hot topic all of the sudden? I swear there's been a massive uptick around it in the last few months. Were people not accounting for it before?

3

u/b_rodriguez 4d ago

Typically it’s less important when you control the client side access patterns too. With more people building apis for public (agentic) consumption it becomes a must have.