not_IO@lemmy.blahaj.zone to Programmer Humor@programming.devEnglish · 1 month agomap reducerlemmy.blahaj.zoneexternal-linkmessage-square20fedilinkarrow-up1383arrow-down14file-text
arrow-up1379arrow-down1external-linkmap reducerlemmy.blahaj.zonenot_IO@lemmy.blahaj.zone to Programmer Humor@programming.devEnglish · 1 month agomessage-square20fedilinkfile-text
minus-squaregerryflap@feddit.nllinkfedilinkarrow-up12·1 month agoYeah that checks out. Now you’re ready for that massively parallel big data (or sandwich?) processing
minus-squareJuanPeece@sh.itjust.workslinkfedilinkarrow-up4·1 month 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-squaregerryflap@feddit.nllinkfedilinkarrow-up1·1 month 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.