71–80 of 80 posts
Here's the full cluster spec: http://redis.io/topics/cluster-spec Looking forward to seeing it taken apart by aphyr. Congrats to Salvatore and the rest of the redis committers!
Then you might want to see both of them on the same stage in June :) http://www.dotscale.io/
Earlier quoted context omitted.
http://memcached.org/ used to be. I haven't done system architecture in about 2 years but when we were looking at in memory databases, it came down to Redis or Memcache. Depending on what you need your database for, there are some that perform better than others. You can check this site for comparisons: http://kkovacs.eu/cassandra-vs-mongodb-vs-couchdb-vs-redis
Redis is normally not in memory. Everything is written to disk and survives a power failure. Memcached is just a cache. Don't store anything there you can't lose.
>In order to achieve its outstanding performance, Redis works with an in-memory dataset. Depending on your use case, you can persist it either by dumping the dataset to disk every once in a while, or by appending each command to a log.
What is the best alternative for redis?
Earlier quoted context omitted.
Yes, he is not doing Jepsen at the moment. The end of his last blog post on it has some explanation. That said, I wouldn't wonder if he'd make an exception, given that it's Redis...
He's been tweeting about Jepsen tests on Aerospike lately: https://twitter.com/aphyr/status/582653874894282752 .
Earlier quoted context omitted.
It's hard to imagine every service in your infrastructure implementing SSL would be more secure than a single VPN tool. You are very optimistic about the difficulties of getting security right.
It's really simple to imagine and I even have implemented it :) "One single VPN" may (and will) fail sometimes, so count your complexity and stability with and without one extra service.
Implementing SSL is easy. Implementing SSL correctly is very difficult, and you probably won't find out you did it wrong for a long time, if ever.
Earlier quoted context omitted.
Redis is normally not in memory. Everything is written to disk and survives a power failure. Memcached is just a cache. Don't store anything there you can't lose.
Not sure that's quite right. From the docs: >In order to achieve its outstanding performance, Redis works with an in-memory dataset. Depending on your use case, you can persist it either by dumping the dataset to disk every once in a while, or by appending each command to a log.
At a previous job people started using Redis thinking it was a fast in-memory data store. It turned out we had accumulated tens of thousands of records.
I haven't measured, but I doubt it's much faster than Postgres. It does have other nice features. I like using the expiring records for caching.
Earlier quoted context omitted.
I understand your reasons and nevertheless hope that you can realize that you are still contributing to April Fool's insanity by making it that much harder for people to tell what is serious and what isn't on this day of disregard. You’re totally within your rights here. I just beg you to consider the audience.
Won't someone please think of the childr...er, developers!
Earlier quoted context omitted.
It's really simple to imagine and I even have implemented it :) "One single VPN" may (and will) fail sometimes, so count your complexity and stability with and without one extra service.
I'm sorry to be skeptical, but when a random person on the internet claims to have implemented SSL more securely than open source tools that are completely built around security, I tend to not believe it. Implementing SSL is easy. Implementing SSL correctly is very difficult, and you probably won't find out you did it wrong for a long time, if ever.
Still no SSL, so using redis-client still just spews your password out all over the internet.
Transport security is mostly better implemented via ipsec (a VPN tunnel). I'm happy that redis doesn't implement SSL, it just shows that they are prioritizing relevant features.
Also solutions like stunnel create a separate process that has to be managed. If I have one for redis, and then one for something else it is harder to tell them apart, because both will be named stunnel.