Redis 3.2.0 is out

Thanks, I really receive good sentiments from the community. I've the feeling that this is not due just to the fact that many developers find Redis useful. It has very serious limits like many other softwares. It is that so far Redis was never proposed as "The Shit", the silver bullet that will save you from your data problem. Is just something I and the other contribs try to do with love, without pretending we are going to save the world. I wish this vision was a bit more common, but (un)fortunately data now is an hot topic with too much money on the table, so feelings are a bit over excited sometimes.

EDIT: Many marketing/business people basically don't understand that you cannot over-sell to developers. The effect is the contrary, you turn people down when you try to say you did something too cool to be true, so this strategy also does not work in the long run.

The attemps at a distributed version were harshely criticized...

What I like about Redis is that, like a mechanical watch, the insides are as elegant and nice as the user experience.

Haproxy is there too...

Postgres? :)

I love redis.

> What do you use it for?

The answer to this question is one of the reasons I like Redis so much. It's not one thing, it's many things!

I've used it for a "dumb" cache (key => bytes), a "smart" cache (key => data structure), a message queue, a pub/sub engine, and even a lock manager.

For many of these use cases it's the best, for others, it's more than good enough and not having to add additional infrastructure components to a system is always a plus.

I can second GeoNames. Sometimes it's hard to beat free. We take a couple files from their dump[1] (primarily the city data) and import into a database. We can then geolocate a lat/long to the closest city.

1. http://download.geonames.org/export/dump/

I'm using it for a photo app (I only need town/city level granularity), and it works well for my needs. Note that the dataset is based upon populated places though, so YMMV if you need to lookup somewhere in the middle of nowhere.

Here is a JavaScript library I wrote for it, along with some scripts for munging the GeoNames dataset:

https://github.com/lucaspiller/offline-geocoder/

If you need higher granularity, take a look at this OSM project:

https://github.com/twain47/Nominatim/

I was turned off by their blurp that their US zip codes database contains only 21k zips out of 41.5k. Are they sufficiently complete for small towns?

More specifically, the OSM project Nominatim does Address->Lat,Lon

http://wiki.openstreetmap.org/wiki/Nominatim

Probably a good time to move to sha256 instead of sha1. https://sites.google.com/site/itstheshappening/

Have you looked at Let's Encrypt for the redis.io domain?

Hey Paul, we have this feature added as a Lua script, but adding it in a native way could be interesting actually. Itamar Haber wrote the Lua script and was pushing for adding it in a native way, I wanted to check after the release the actual demand for it.

I work on a SaaS spatial product and had to come up with a solution to the same point/boundary problem. It needed to be 'fast' (ideally <3s) when filtering, rendering, styling and summarising 100k points within 43k polygons (so say 100k shop locations within many state, county and zip/zcta codes in US). DB is Oracle 11g for several reasons: product is larger and older than this requirement, small team has solely expertise with oracle and zero commercial experience with nosql dbs (good devs though and have showed interest in and toyed with nosql dbs) plus standard budget/time constraints.

Solution was to add a hidden column for each administrative category (e.g. for US: region, state, county, zcta) to each point record to replace spatial searches with filtering.

Would something like that work for you? What kind of numbers of points and polygons are you looking at and how quickly do you need to solve the problem?

> My problem with many existing geo implementations is they assume that a circular radius is the query type I care about

Really? Wouldn't most GIS implement something like OGC Simple Features? AFAIK all SQL GIS implementations follow that (to various levels of completeness, but even MySQL has shapes support since 5.6)

You can already do this using BITSET -- I tracked 100 million objects with incremental integer keys during a migration process and it worked great.

From what I read, BITFIELD behaves differently -- it treats your data as a series of "packed" bits. So while with BITSET you operate on each bit individually, with BITFIELD you operate on a series of bits with a starting offset, and you have to be mindful of the length.

nice! didn't realize thats how that worked.