One thing worth pointing out - that the approach described in TFA changes PUSH architecture to PULL.
So now you have to deal with deciding how tight your polling loop is, and with reads that are happening regardless of whether you have messages waiting to be processed or not, expending both CPU and requests, which may matter if you are billed accordingly.
Not in any way knocking it, just pointing out some trade-offs.
So now you have to deal with deciding how tight your polling loop is, and with reads that are happening regardless of whether you have messages waiting to be processed or not, expending both CPU and requests, which may matter if you are billed accordingly.
Not in any way knocking it, just pointing out some trade-offs.