struct time {
Kyle @stockholmux shows a nice trick for doing a stack latency analysis. CAUTION: don’t run blocking Lua scripts in production, unless you mean trouble.
Same Kyle @stockholmux, different post. If a callback is never called back is it still a callback? Philosophy aside, the reality is the sometimes you need to time out a call and this is how you Node that.
Time series are quite useful but trying to fit them into Redis can be unintuitive to the uninitiated… until you read this as-usual-top-notch piece by Markus Bergholz @markuman. Pretty simple now, right?
};
struct highscalability {
Karl Stoney @karlstoney put down what needs to be done to make a single IP endpoint for a Redis HA set with HAProxy – simple and sweet.
Want scalability and want to do it on your own? Head over to Iccha Sethi @IcchaSethi‘s post where she cracked this one for you.
Don’t let the name fool you – rb means redis blaster and besides having the COOLEST. LOGO. EVER. it also promises to be the fastest way to talk to many Redis nodes. KABOOM! by Armin Ronacher @mitsuhiko via Sentry @getsentry
Nice to see that @ObjectRocket is now allowing their users to scale Redis, even if only up is self service. I guess they’ll need to support clustering before Derek Johnson @derekjohnson70 can tell the users to stop spending time and thoughts on scaling 😉
}; // todo: use Redis Cloud or RLEC - so much simpler
An update (see RW#3) from Bronto Software @bronto – Tom’s words are exciting but I couldn’t find the code anywhere… Help?
This is a classic example of what makes us engineers tick – to study something we examine it, try it out, take it apart, scrutinize its parts, modify something, put it back together, repeat, lather and rinse, and not necessarily in that order. Parker Selbert @sorentwo demonstrates the meaning of Redis’ intelligent caching with a lovely study of hash optimizations (bonus points for the interactive graphs :)).
Living up to his nick (at least in this issue that is), Parker Selbert @sorentwo delivers a second piece, this time about my favorite scripting language in Redis and when to use it.
OH @yburyug > @robertfriberg Will do. I’m working on an essay on the history of them from CODASYL onwards to the creation of Redis (the first GREAT nosql)
Although it is already high summer, it is never too late for Spring. This one is an example that should quickly get you started with Spring Data – via Java Code Geeks @javacodegeeks #IRejectTheFreeEbooks
Francis Alexander @torque59 updated his framework with new modules that target innocent Redis instances in the wild with potential attack vectors. While it is important to know about these “vulnerabilities”, the first and most important step in resolving any security issue is USE A PASSWORD.
Reads like good whiskey (or maybe vodka?) and hits just the right point – awesome a-lot-of-what-you-need-know-about-Redis-data-structures-in-one-page from Morgun Ivan @proft
Continuation of the project (see RW#52) from Raymond Ranelli @RRanelli.
“A config driven redis client factory that pools” – sounds useful.
OH Andrew Newdigate @suprememoocow > The correct way to use the Redis LATENCY DOCTOR command:
`redis-cli LATENCY DOCTOR|say -v Fred` #HAL9000 <- #RedisProTip
Crystal is da bomb – by Stefan Wille @stefanwille.
Now that is really useful – one ring to bring them all and in the darkness bind them by the Close.io @closeio team.
Now that is something that is always fun to see – a new Redis client, this time in for Racket @racketlang.
Unpretentious and appears to deliver the goods needed to get you started on your own chat app or similar – by Ash Singh @Ash_Singh4u
OH Hayden Jones @work_op > Saying redis is only useful for k/v is like saying Linux is only useful for libc
