alt Hacker Newsin high scale stateless app services this approach is typically used to lower tail latency. two identical service instances will be sent the same request and whichever one returns faster “wins” which protects you from a bad instance or even one which happens to be heavily loaded.
Replies
lanstin • last Saturday at 8:21 PM
And the tail latencies are wildly improved with each addition dup. Has to be idempotent of course.
I'm not sure I follow. In this instance we're talking about multiple backend matching engines... Correct? By definition they must be kept in sync, or at least have total omnipotent knowledge about the state of all other backend book states.