@not_IO@lemmy.blahaj.zone to Programmer Humor@programming.devEnglish • 9 days agomap reducerlemmy.blahaj.zoneimagemessage-square14fedilinkarrow-up1376arrow-down10file-text
arrow-up1376arrow-down1imagemap reducerlemmy.blahaj.zone@not_IO@lemmy.blahaj.zone to Programmer Humor@programming.devEnglish • 9 days agomessage-square14fedilinkfile-text
minus-square@gerryflap@feddit.nllinkfedilink12•9 days agoYeah that checks out. Now you’re ready for that massively parallel big data (or sandwich?) processing
minus-square@JuanPeece@sh.itjust.workslinkfedilink4•9 days agoAnd then you fuck up your asynchronous timing, leaving a race condition where the sandwich has bread on the inside. Oh, and QA can only reproduce sometimes
minus-square@gerryflap@feddit.nllinkfedilink1•8 days agoWith mapreduce you should generally have your code written in such a way that that cannot happen. Unless the reduce step is improperly programmed.
Yeah that checks out. Now you’re ready for that massively parallel big data (or sandwich?) processing
And then you fuck up your asynchronous timing, leaving a race condition where the sandwich has bread on the inside. Oh, and QA can only reproduce sometimes
With mapreduce you should generally have your code written in such a way that that cannot happen. Unless the reduce step is improperly programmed.