5 ms·

> Compatibility with the Redis protocol means you can migrate your applications with zero code changes. Does this mean they don't actually use Redis, but have

by pcx 8y ago

> Compatibility with the Redis protocol means you can migrate your applications with zero code changes. Does this mean they don't actually use Redis, but have an alternate implementation of the protocol? In such a case, wouldn't it be different it terms of performance when compared to the original one. Also, keeping up with new versions should be a major overhead. If Google is still doing an alternate implementation, I wonder what could be the reason.

jkaplowitz 8y ago
It's probably built on top of Google's standard production software and hardware stack, the same thing they use to run most of their standard services like search and Gmail. This tech stack tends to have evolved earlier than and separately from the public equivalent. It generally scales and performs better than normal tech stacks, but its components are so different and so mutually interdependent that it's bad at directly running normal software. The protocol, however, can be implemented just fine. To be clear: Even though I worked at Google in the past, I don't now, am not speaking for Google, and know nothing secret about this product. I'm extrapolating from widely known general knowledge about Google's technical infrastructure.
mk89 8y ago
It's the same with Aws elasticache. There is redis underneath, still, if you want to have all the features that they provide - scale in/out, replicas, etc, you'll need to have some tools around. I would say yes, it's still different than using the original one, but that's the way it is when you use any managed service.
paxys 8y ago
Will be different, yes, but in the same way any two instances of "real" Redis will be different. Hardware, networking, routing, load balancing, memory and disk IO, number of instances, backups/failovers etc. are going to be deciding overall performance rather than the Redis binary itself.
Lunatic666 8y ago
We have a Redis+Memcached frontend with an Apache Ignite Backend. Now we can re-use existing functionality in the clients and have new features like read-through based on a MySQL database or an automatically updated near cache on the instances themselves.
- ddorian43 8y ago
  Are you talking about this https://apacheignite.readme.io/docs/redis https://apacheignite.readme.io/docs/redis If yes, that's 5% redis features.
gcbirzan 8y ago
It's not an alternative implementation. I've been on the alpha and some of the bugs were actually bugs in the OSS redis.

by pcx 8y ago

jkaplowitz 8y ago

It's probably built on top of Google's standard production software and hardware stack, the same thing they use to run most of their standard services like search and Gmail. This tech stack tends to have evolved earlier than and separately from the public equivalent. It generally scales and performs better than normal tech stacks, but its components are so different and so mutually interdependent that it's bad at directly running normal software. The protocol, however, can be implemented just fine. To be clear: Even though I worked at Google in the past, I don't now, am not speaking for Google, and know nothing secret about this product. I'm extrapolating from widely known general knowledge about Google's technical infrastructure.

mk89 8y ago

It's the same with Aws elasticache. There is redis underneath, still, if you want to have all the features that they provide - scale in/out, replicas, etc, you'll need to have some tools around. I would say yes, it's still different than using the original one, but that's the way it is when you use any managed service.

paxys 8y ago

Will be different, yes, but in the same way any two instances of "real" Redis will be different. Hardware, networking, routing, load balancing, memory and disk IO, number of instances, backups/failovers etc. are going to be deciding overall performance rather than the Redis binary itself.

Lunatic666 8y ago

We have a Redis+Memcached frontend with an Apache Ignite Backend. Now we can re-use existing functionality in the clients and have new features like read-through based on a MySQL database or an automatically updated near cache on the instances themselves.

ddorian43 8y ago
Are you talking about this https://apacheignite.readme.io/docs/redis https://apacheignite.readme.io/docs/redis If yes, that's 5% redis features.

gcbirzan 8y ago

It's not an alternative implementation. I've been on the alpha and some of the bugs were actually bugs in the OSS redis.