January 2019
Intermediate to advanced
378 pages
11h 35m
English
Imagine a bank's debit API failed immediately after deducting some amount from the client account. However, the client doesn't know about it (as it didn't get any response from the server) and reissues the call to debit! Alas, the client loses money. So how can a service implementation handle messages/data and produce the same results, even after multiple calls?
Idempotent is one of the fundamental resilience and scalable patterns, as it decouples the service implementation nodes across distributed systems. Whether dealing with data or messages, the services should always ...
Read now
Unlock full access