TLDR: One of their five Postgres clusters went into read-only mode due to an Transaction ID Wraparound issue. Restoring this can take up to several days (!).
Heads-up: There is no overview/confirmation page at the end of the signup process, so no reviewing your answers before submitting. Just found this out the hard way!
We have been looking into a good solution for our office dashboard last month. Evaluated a lot of solutions like Geckoboard, but eventually ended up using Databox.com. Beautiful dashboards and also mobile apps.
I've been working on Repuso the last few months after a similar service closed down. After their closing down notice i whiped up an MVP in a weekend and started testing it with some users of the old service.
The last few months it grew into a mature service which lets you showcase social media testimonials with a single line javascript widget. All Facebook, Twitter, Instagram, Zendesk and Delighed user feedback can be displayed on your most important pages to increase the conversion of your website.
Dynamic Redis (which is a Redis Fork that lets you add modules to it) is a great find! Especially with the Geo module added.
I needed a limit parameter for the Georadius method because i wanted a result set sorted by distance in a large radius, but not have thousands of results send from the redis server to my webservers. Anyone interested in such a parameter can use my little fork for the Geo module:
Great Salvatore! Could you make the max distance parameter optional? Sometimes i just want the nearest items, even though they could be on the other side of the world.
One of our applications has user generated content with a geolocation attached to each of the items. For several selections we want to show the top 10 nearest items. If they are only a few, the radius has to be very large to have some items in the result set.
Currently the Geo module only supports a range up to 20.000 km. So your idea does not work at the moment. I agree that those items are not really "nearby", but to be consistent through out the application it would be nice to be able to select without a max distance.
As i understood this your database storage is replicated to multiple places, but it still runs on one instance. It does not have failover to those replicated places. You'll have to launch multiple instances for that just like RDS. So cheaper, no.