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)
[deleted]
ApsaraCache: A Redis branch originated from Alibaba Group
31–40 of 43 posts
Re: ApsaraCache: A Redis branch originated from Alibaba Group
#32Reminds me of HHVM: a specific solution developed by a specific team for their specific problem. Might help Redis on the long run though: some ideas might be brought back to Redis, or at least it will bring some challenge to the devs. Meanwhile, keep calm and use Redis ;-)
Agreed, though HHVM went on to be deployed at some other small websites [1]. Maybe this will too.
Re: ApsaraCache: A Redis branch originated from Alibaba Group
#33One of the most useless FAQ I saw. I would have been more interested in knowing the improvements or changes made when compared to Redis. I had some trouble with large scale master slave Redis configuration. I was hoping if they have solved the issues.
They list the two things they changed compared to redis in the readme.
I went back and read again. "ApsaraCache is based on the Redis official release 4.0 and has many features and performance enhancements" - I could find only memcache and performance improvement. Now Membache has nothing to do with Redis, its something not improving Redis, and 30% performance improvement is very vague statement with no other supporting benchmarks and documents. When they say many, I can't see any other than these two.
Re: ApsaraCache: A Redis branch originated from Alibaba Group
#34This 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)
Kind of sad how things can't be partial and in the process of being open-sourced, no they have to be complete or they are "jokes".
Re: ApsaraCache: A Redis branch originated from Alibaba Group
#35Earlier quoted context omitted.
They list the two things they changed compared to redis in the readme.
I went back and read again. "ApsaraCache is based on the Redis official release 4.0 and has many features and performance enhancements" - I could find only memcache and performance improvement. Now Membache has nothing to do with Redis, its something not improving Redis, and 30% performance improvement is very vague statement with no other supporting benchmarks and documents. When they say many, I can't see any other…
They implemented the memcached protocol on top of redis.
Also,
> There are many features in ApsaraCache, the following two are included in this release and the other features will be gradually released in the subsequent, so stay tuned.
Re: ApsaraCache: A Redis branch originated from Alibaba Group
#36Reminds me of HHVM: a specific solution developed by a specific team for their specific problem. Might help Redis on the long run though: some ideas might be brought back to Redis, or at least it will bring some challenge to the devs. Meanwhile, keep calm and use Redis ;-)
Agreed, though HHVM went on to be deployed at some other small websites [1]. Maybe this will too. 1. http://hhvm.com/blog/7205/wikipedia-on-hhvm
On the other hand, Wikipedia is going to have to migrate back off of HHVM now that Facebook is planning to break compatibility with PHP and focus totally on Hack [0]. So hopping on board someone else's solution can bite you if their priorities change.
Re: ApsaraCache: A Redis branch originated from Alibaba Group
#37Earlier quoted context omitted.
Agreed, though HHVM went on to be deployed at some other small websites [1]. Maybe this will too. 1. http://hhvm.com/blog/7205/wikipedia-on-hhvm
On the other hand, Wikipedia is going to have to migrate back off of HHVM now that Facebook is planning to break compatibility with PHP and focus totally on Hack [0]. So hopping on board someone else's solution can bite you if their priorities change. [0] http://hhvm.com/blog/2017/09/18/the-future-of-hhvm.html
> Facebook is planning to break compatibility with PHP and focus totally on Hack
Ok...
> Wikipedia is going to have to migrate back off of HHVM
Why?
Re: ApsaraCache: A Redis branch originated from Alibaba Group
#38Earlier quoted context omitted.
On the other hand, Wikipedia is going to have to migrate back off of HHVM now that Facebook is planning to break compatibility with PHP and focus totally on Hack [0]. So hopping on board someone else's solution can bite you if their priorities change. [0] http://hhvm.com/blog/2017/09/18/the-future-of-hhvm.html
> Facebook is planning to break compatibility with PHP and focus totally on Hack Ok... > Wikipedia is going to have to migrate back off of HHVM Why?
For years, HHVM had a significant edge in performance and a significant handicap in compatibility. Today, PHP7.1+ is ~at parity in performance but the community still has not fully embraced HHVM. In fact, some flagship projects like Symfony even stopped on purpose. Increasingly, the main reason remaining for running PHP on HHVM is if you really want static typing - and this is not a natural preference for most PHP teams.
Re: ApsaraCache: A Redis branch originated from Alibaba Group
#39Earlier quoted context omitted.
On the other hand, Wikipedia is going to have to migrate back off of HHVM now that Facebook is planning to break compatibility with PHP and focus totally on Hack [0]. So hopping on board someone else's solution can bite you if their priorities change. [0] http://hhvm.com/blog/2017/09/18/the-future-of-hhvm.html
> Facebook is planning to break compatibility with PHP and focus totally on Hack Ok... > Wikipedia is going to have to migrate back off of HHVM Why?
Hack/HHVM is breaking compatibility with PHP. MediaWiki is a large PHP software project. Other MediaWiki users run the software in non-HHVM environments.
Re: ApsaraCache: A Redis branch originated from Alibaba Group
#40This 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)
Please don't post uncharitable dismissals of other people's work to HN. If you read https://news.ycombinator.com/newsguidelines.html properly you'll see that doing this breaks more than one of the site guidelines.