813 karma · joined January 15, 2014
So, despite the obvious perks that we'll enjoy by side-loading our own junk, antirez's "Quality or DEATH" approach on this matter leaves no open questions about the possible inclusion of this functionality. There is, however, another way to get code running in Redis... it is called a GitHub Pull Request :) If you've thunk up something really amazing/useful and coded it, drop by the redis-dev mailing list to discuss it, maybe do an RCP and submit your code. No one promises that your PR will be accepted, but even if it won't make its way into the core, anyone will be able to use it nonetheless.
Another point worth mentioning in this context is that in order to even contemplate such a mechanism, Redis' core will need heavy refactoring of the internal API. This is by all accounts a huge effort that, if taken by the developer, is likely to postpone a lot of other important work.
As for goodness @ the Pivotal site, this is one of my favorite - dying to see it grow: https://support.pivotal.io/hc/en-us/categories/200308268-Ope...
Besides Pivotal's commercial support for Redis (which, from what I've heard, is superb) there are also at least two hardcore Redis community members who're providing professional support for Redis deployments - for more details, contact Michel Martens and Damian Janowski.
Redis Labs, my employer, is also heavily into Redis (duh) so naturally we give support for our product line that consists of a Redis on-prem solution and a cloud service.
Your arguments are exactly what I had wished for - your POV is just as crucial and my only regret is that we didn't "demand" that you go on stage then and there to present it - I would have certainly stayed for that and the ensuing discussion no matter how long it would have lasted after closing time (although, in second thought, that would have been extremely unfair as you would have been pushed into a tight spot w/o preparation, so I take that back). I could offer my views on each of the points but that's hardly relevant IMO, useless :)
What really pains me is seeing you two beautiful and smart individuals, who are passionate about the same thing, disagreeing so heatedly over these issues. I think (hope?) I can see where each one of you is coming from and to me it doesn't look like your goals are that different. Perhaps the nature of an open source community is such that such topics needs to be vented out in public - /me don't know. I sincerely hope that the core team will find a way to overcome these differences because despite of (or maybe because of) them, from a bystander's POV, it looks to me like you have a good thing going - together and backed by an amazing community.
I've attended that session and have had the pleasure of being exposed to Matt's views in other occasions (IRL and online :)). While I don't necessarily agree with everything Matt says, his perspective is unique - he's the only 0.5 core Redis developer in the world and his contributions to the project are mostly inspiring and certainly of quality. From what I've seen, he's devoted to Redis as much as anyone can be and takes the project very (too?) personally.
Matt's presentation skills are also kinda unique - he uses at least 2^32 slides in every talk, and these are mostly filled with cartoons/memes that I'm too old to recognize mixed with geeky jokes that he makes up by himself ("What is the favorite food of villains? configs." - brilliant!) (remember that even making up a bad joke takes considerable talent.)
However, between the puns and laughs, his talk is honest and his messages are clear. He usually (I missed the first 2m of this session [i.e. first 200 slides] but I'm guessing he did it this time as well) opens with an apology for his upcoming rants. Then he delivers sharp criticism at what he perceives to be faults based on his 1st-hand experience. Instead of accepting the "facts", he challenges them and tries suggesting creative approaches to solving these problems.
Yes, he could be a better politician but maybe he doesn't want that (anymore?) - it seems that he wants to make the (Redis) world a better place by acting. He uses shock to deliver his points, and perhaps that's excessive at times, but I give him the credit because he tries practicing what he preaches. Matt has his reasons for choosing this rhetorical style - maybe he'll change it after this experience (although mostly likely he won't) - and quoting out of context is often ill-perceived even when well-intended, but when you listen to what he says rather than the how, he certainly shines a hard and clear light on some uncomfortable facts. Perhaps these [facts] are immutable, perhaps they can be tweaked and optimized for joy - I can't claim I know any better... but he definitely stirs things up and ignites thought-provoking discussions... and perhaps that's all that's needed.
I don't think Salvatore should or can be "replaced" by Matt, or by anyone else for that matter, until if and when Salvatore decides so. I don't believe that anyone with an IQ above 42 seriously thinks that Salvatore hasn't been or isn't committed to Redis. I didn't interpret Matt's talk as a coup attempt but rather as the continuation to previous discussions about scaling Redis' development. I can't imagine Matt was thinking that he'll be overthrowing the Benevolent Dictator during Redis Conf's last session - my impression of the talk was that in his own Matt-ish way, Matt was trying to shock everyone, and specifically antirez, into action to better things. It is the maintainer's right and obligation to choose between merging, cherry-picking from or even entirely rejecting Matt's orally-submitted PR, but I really don't see that PR meant as a personal attack. My 2c.
Alternatively, if you want to continue using Redis - with the current or a slimmer version of the data model - without having to worry about machine upgrades or clusters, then I recommend that you look at http://redislabs.com/redis-cloud (disclaimer - I work at Redis Labs). Our managed service is built using production-proven Redis clusters that allow your database to scale well beyond the limits of any single node, without you having do anything or change a line of code.