This article in my opinion missed a few key points: Redis is not different than Disque, I don't use Redis since basically the start of the project for any serio

This article in my opinion missed a few key points: Redis is not different than Disque, I don't use Redis since basically the start of the project for any serious thing, since Redis took over my other occupations in a matter of months. I believe I did a reasonable job in still creating the right abstractions for the users, even not being myself a direct user of Redis. Just two examples: Lua scripting and sorted sets, among the top Redis used features, where both conceived while I was no longer using the system first hand. I think I can repeat the same with Disque, since I'm not an user, but the design is an effect of what users experience and complain about Redis as a message queue. Moreover both for Redis and for Disque in the future I'll be working more with people having large deployments and use cases in order to get more feedbacks about what could be useful things to add. I don't want to sound immodest, but the rule that you have to be an actual user of the software to create something decent does not necessarily applies to anyone, there are people that can synthesize the needs and design APIs without actually implementing anything serious. However note that don't implement anything serious does not mean don't implement anything at all. I created several "toy projects" using Redis over the years, and I'm doing the same with Disque.