I’ve played around with Redis again as part of a logging system, having used it as a really basic queue system in a previous life. I may not play with it immediately but there is a lot to chew over in the post about writing scripts against Redis.

Initially I’m looking at trying to write a search script for a day’s worth of logs, so nothing major but I’m also hoping to capture counts for services and parts of a platform being used. It’ll probably have a very few defined commands to avoid bloat although it will initially be in PHP (since I’m using it for other parts of the platform). It might change into a different language (Lua seems to be the one being muttered about) if performance requires it.

It has been a while since I’ve really played with Redis but I’m glad to come back to it and become re-acquainted with it.

Our base is database is MySQL which I like a fair amount for what we do with it but all I needed do was to cache some data. The scripts write a fair amount of data to the cache and then there is one read process to read the entire list before updating the main database. At least I know that the data has some sort of security. It is not a panacea or similar cure all but it does have a place in development for certain jobs.

Best tool and all that?

I can understand why Twitter are not using Cassandra in the main service but are still using it for other projects.  For now. Systems and priorities change and perhaps it will happen in some way.

Despite its meteoric rise, NoSQL is not the answer to everything. It does have a useful place though.