News for hackers. Stuff that matters.
Re:5 subtle ways you’re using MySQL as a queue, and why it’l... by brndnhy on Friday September 16, 2011 @03:28AM (#3003512)
Yeah, that's true. But my environment is such that any one of 100 or so app servers has a significantly lower chance of running out of memory than the Redis server does.

The 0MQ high water mark is set high enough so that it's virtually impossible not to fix a broken DB by the time messages on the client side create an OOM condition being queued in memory.

Re:5 subtle ways you’re using MySQL as a queue, and why it’l... by moe on Friday September 16, 2011 @07:53AM (#3004081)
high enough so that it's virtually impossible not to fix ... by the time

I'll add that to my "famous last words" fortune cookies.

Re:5 subtle ways you’re using MySQL as a queue, and why it’l... by rbranson on Friday September 16, 2011 @03:52PM (#3006018)
Ultimately, it's all about the odds. That's what HA, replication, and DR are all about. It's so statistically unlikely for certain things to happen, they just fall out of the realm of reason. Most operations folk I've talked to don't even consider their disaster recovery plans to be within the realm of feasibility. The chances of a catastrophic event rendering the owners of the system defunct is many orders of magnitude more likely than an event that breaks the standard data fail-safes that most datacenters have in place.