21–30 of 43 posts
Note that this branch is based on Redis 2.8 so of course porting stuff requires some work.
Hi all, I'm here in Hangzhou and had the pleasure to have a meeting with the team working at that. It's a great team and we'll work into merging stuff into upstream Redis when it makes sense. It's cool that companies other than Redis Labs are starting to contribute to the development! Note that this branch is based on Redis 2.8 so of course porting stuff requires some work.
Goals: For both support Redis and Memcached protocol with no client code need to be modified. For highly stable and efficient in production environment. At face value it appears to be a NIH driven development. It is not only a redis fork it is also a persistent memcached port, which is _only_ selectable on launch. Maybe there is a catch, but lack of a roadmap and/or design document certainly doesn't really help.
Hi all, I'm here in Hangzhou and had the pleasure to have a meeting with the team working at that. It's a great team and we'll work into merging stuff into upstream Redis when it makes sense. It's cool that companies other than Redis Labs are starting to contribute to the development! Note that this branch is based on Redis 2.8 so of course porting stuff requires some work.
Can I ask what you think of pedis ? (see my other comment on the thread)
Hi all, I'm here in Hangzhou and had the pleasure to have a meeting with the team working at that. It's a great team and we'll work into merging stuff into upstream Redis when it makes sense. It's cool that companies other than Redis Labs are starting to contribute to the development! Note that this branch is based on Redis 2.8 so of course porting stuff requires some work.
Hmm. The Github repo says it's based on 4.0: "ApsaraCache is based on the Redis official release 4.0" (from https://github.com/alibaba/ApsaraCache/blob/develop/README.m...)
I wonder if Redis throughput is even a problem in practice. People usually add nodes to get more capacity (memory).
For most use-cases, Redis nodes will saturate network IO before CPU, but it should be noted that Redis is single-threaded so YMMV.
Hi all, I'm here in Hangzhou and had the pleasure to have a meeting with the team working at that. It's a great team and we'll work into merging stuff into upstream Redis when it makes sense. It's cool that companies other than Redis Labs are starting to contribute to the development! Note that this branch is based on Redis 2.8 so of course porting stuff requires some work.
>Note that this branch is based on Redis 2.8 Hmm. The Github repo says it's based on 4.0: "ApsaraCache is based on the Redis official release 4.0" (from https://github.com/alibaba/ApsaraCache/blob/develop/README.m... )
This project is some kind of a joke; Look at the commit history; https://github.com/alibaba/ApsaraCache/commits/develop 15 are "writing of README / adding my copyright", and 2 are actual feature (and not long)