Letting a big problem eat yourself away besides sleep, knowing you're the only person to make it happen, and eventually solving it. However, real truth, planning out a big operation for a few weeks. Server migrations are the best. Knowing there's so much to go wrong. But you're prepped. Pop in Eye of the Tiger, terminals maxed out and you just make it happen. That's higher than jumping out of a plane when you love what you do.
Paypal Adaptive Payments for chained payments which allows splitting of proceeds at a percentage between one or more partners. When it works most of the time it's great, but there is no recurring API forcing you to use preapprovals and those have a lot of restrictions and caveats. Amazon FPS is only other provider I'm aware of that provides similar functionality.
Push if list exists. This are the operations that are at the base of the twitter Redis caching implementation.
This operations are useful every time you want to use Redis for caching timelines, as the idea is: if this user is already in cache (at least a single item exists) then push against the cache, otherwise not.
Perhaps, but the description essentially said that there is a custom python layer that aggregates the data, and they punt it into MongoDB with some SQL extraction pattern simply to store it into that silo.
e.g. If I run a query for NAME LIKE 'BLAH%' it stores that resultset. If I run NAME LIKE 'BLAP%' it stores that resultset. If someone else comes and runs either of them, only a direct match will pull my prior results.
