Re:How We Built the Software that Processes Billions in Paym...
by ary on Thursday June 30, 2011 @03:00PM
(#2715307)
Probably because the data transformations and storage required to complete a transaction need to be handled by a coherent version of their code. Processing payments with a half-updated stack sounds painful and error-prone.
Re:How We Built the Software that Processes Billions in Paym...
by fleitz on Thursday June 30, 2011 @02:59PM
(#2715305)
Because schema changes and deployments are generally non-atomic, running a transaction through an untested configuration (front-end code = 1.0, schema = 1.2 and backend = 1.0) generally results in unknown things happening. When dealing with money people generally prefer right to fast.
Re:How We Built the Software that Processes Billions in Paym...
by Swannie on Saturday July 02, 2011 @06:02AM
(#2721387)
This one made me go "Huh?" and reread.
I don't understand why you'd need a custom HTTP server. It might be overly simplistic, but just write a module for nginx? Surely that would have been faster. You get controllable timeouts, you could tweak their throttling code to stop it throwing 50x, and modify/take inspiration from nginx-ey-balancer. And you get a bullet proof HTTP engine for free?
Why is it necessary to suspend traffic to make these kinds of changes? Just curious.