Traditions, much like deadlines and rules, are made to be broken (btw, what do you call a tradition of breaking traditions and do you have break that one too?). It has been twice now that on April's fool, Redis' Lead Dev Salvatore Sanfilippo @antirez had announced somethingawesome. Today, however, the announcement is that there is no announcement… or rather, that the announcement will be made within 1 month and 10 days at RedisConf 2016 (register for free with the RLCONF16 promo code).
If you want a hint as to what that announcement is going to be, feel free to reach out but my lips are sealed.
Redis Trivia: 2^64, or 18,446,744,073,709,551,616, is the total number of 0.5G string values that a Redis database can store.
@Netflix's "EVCache is an extensively used data-caching service that provides the low-latency, high-reliability caching solution that the Netflix microservice architecture demands. It is a RAM store based on memcached, optimized for cloud use." It is designed for caching databases and memoization, but also offers strong global consistency (or eventual) and cross data center replication. The Replication message queue is handled with Apache Kafka with proxied relay clusters. By the EVCache's team: Shashi Madappa, Vu Nguyen, Scott Mansfield @sgmansfield, Sridhar Enugula, Allan Pratt and Faisal Zakaria Siddiqi @faisalzs
And not apropos, a couple of weeks ago, while working with GeoJSON, I was trying to load some bulky contents to Redis. I know of at least two Bashclients, but both were too robust for my humble needs. Then came a question from the community that had pushed me to share this.
If you're using the Tryton ERP project this could be useful. If not, just appreciate the ease of using Redis to monitor an application's performance including access to the primary database – by Ali Kefia @alikefia.
"…is a geolocation data store, spatial index, and realtime geofence. It supports a variety of object types including lat/lon points, bounding boxes, XYZ tiles, Geohashes, and GeoJSON. Seems useful, definitely instructional and very reminiscent of something extremely familiar – from Josh Baker @tidwall.
So that's actually cool in two ways, the first is obvious – I mean, who doesn't want to crack Redis, right? The second nice thing has to do with Redis and Nmap in general, so if you're idle scan through Nmap's docs to figure it out. Modules courtesy of Vaggoc Deirme @edeirme.
This one has no trivia, it is just a brute force attacker – protect yourself by following this quote from the default redis.conf configuration file:
# Warning: since Redis is pretty fast an outside user can try up to
# 150k passwords per second against a good box. This means that you should
# use a very strong password otherwise it will be very easy to break.
I had the pleasure of actually attending Daniel Magliola @dmagliola's session at El Rug @lrug – if you already know your Redis, I recommend that you keep scrolling until the part about the phone rotator use case. Good stuff.
If there's going to be only one Redis event that you'll go to this year, this should be the one. Register for free with the RLCONF16 promo code and if you hurry, the call for papers is still open (but not for long)!
By continuing to use this site, you consent to our updated privacy agreement as described here. You can change your cookie settings at any time as described here but parts of our site will not function correctly without them.