I know that both Microsoft and Richard Stallman have gotten a little older and a little wiser…but I certainly never expected a meeting of these two minds.
Well, it’s that time of year again, where Redis Day storms the ports of New York, brandishing corporate video that implies Redis is the only hope for humanity’s salvation. I don’t know if that’s necessarily true, but like last year, they do know how to pick a location. In any case, the first of the 2-day event was an introductory session to Redis, not really necessary for those already familiar with the platform. I opted to go out of curiosity, and I’m glad that I did.
Even though most of the day was a rehash of what I already knew, the intro did point out to me some features that had been added with the most recent version, like the UNLINK command. (I’m not known for always reading release notes.) I also learned that the “master-slave” terminology has now fallen under, as Jacobins would probably describe it, the guillotine of progress:
Actually, I’m not sure if the new “master-replica” terminology is a better set of terms. If you still use the term “master” in this scenario, doesn’t it imply that the other party is a slave? And when I think of replica in this situation, the term replicant comes to mind, and that doesn’t really sound all that much better. But I digress…
The second day of the event was more interesting. To a small extent, some of that could be attributed to the general speakers. We heard from a few people about certain business cases, as they described how Redis was used beneficially in their work. But for me, the best parts of the day were the beginning and end, when we got to hear from the brilliant creator of Redis: Salvatore Sanfilippo (a.k.a., Antirez).
Since most of the time was spent more towards the corporate pitch, it was refreshing to hear Antirez talk about all of the technical features in the newest version of Redis and how the need and implementation for these features came about. All of which was told using his interesting drawing style, which I had never seen a presenter do before. But I definitely appreciated it, since I tend to do the same thing whenever I describe anything with precision. (Even how to properly build a sandwich.) I also appreciated it since he and I probably have the same skill level of drawing:
Even though some people might tune out during these kinds of events (especially at the end, when people are looking to beat the crowd by leaving early), I enjoy the technical presentation as a breath of fresh air. Who knew that a detailed explanation on the evolution of the Redis EXPIRE command could wake me up from my imminent coma? I was just as surprised…almost as much as Antirez was when I approached him later, to thank him for leaving Sicily to speak and to ask him some questions. (Note to self: pay attention to your surroundings and never ask questions of someone when they’re waiting to use the bathroom, especially a database guru. You may not get the best answers, and you will feel a tad awkward when you realize your mistake.)
So, what did I take away from that day? Well, I could say that Redis is definitely growing its user base. Just from a glance and a shoddy memory, I’d say that the crowd was nearly double the size of last year’s event. Plus, I heard about a more diverse set of projects using Redis than ever before. From all that, I would say that it’s becoming a bigger fish in the DB sea.
So I guess the ultimate question is: who’s going to try and eat the growing fish before it gets too big? My money is on Oracle.
The lectures were interesting, but let’s not forget one of the most important purposes of the conference: to reconnect with old friends (of which I spent most of my time towards the end). And connect with new ones! Speaking of which, it looks like Microsoft has decided to move into the neighborhood, complete with their spanking new workbench:
They did a good job trying to sell it, especially for Ethereum users. For the grizzled developers like me, I appreciate that they’re trying to entice more of the enterprise people (i.e., oldtimers) to Ethereum by integrating existing platforms (like BizTalk) with the blockchain. I’m still not sure about their approach with BizTalk, and I still prefer my solution to their solution…but who knows? Maybe it just needs some time to mature.
It seemed like only a few more minutes passed by, but when I looked up at the board, it was practically over!
I could hear the singing that signaled the unfortunate end of the 4-day event. I couldn’t say what was worse: it was already finished for this year, or somebody still thought that it was a good idea to close the show with a sing-a-long in the style of Ned Flanders at Bible Camp.
Minus the singing, I’m already looking forward to next year!
Of course, there were some events that I should have attended but did not (like the Buterin talk), but I lost so much time in conversations with people. Eventually though, on another day of the conference, I decided to pry myself from talking and follow one crowd to a lecture, as everyone poured into one of the larger lecture rooms. I wondered what this talk would be about…and then out walked Emin Gün Sirer! I had heard of him, and I knew that he was doing some work on Serenity…but, ultimately, being the newb that I am, I didn’t actually know in detail. (I learned later that he assists Buterin and others with ideas regarding sharding.) As it turned out, though, this lecture was more of an argument for Avalanche instead of Casper. So, what exactly is Avalanche? Sirer eloquently and amusingly put an end to my ignorance, as he launched into an explanation.
Unbeknownst to me (since I am, in fact, a newb), Casper wasn’t the only popular proof-of-work algorithm that was out there. Where Casper relies on disincentives in its trustless model, Sirer explained that Avalanche relied more on statistics and random sampling. Since all memories of my S&P 101 class in college were now holes in my brain chewed out by chronomice, I’ll admit it: I didn’t understand it completely. But I was still dubious since mischievous behavior wasn’t taken into account. Like Casper’s Vlad Zamfir had said: “We don’t get to take a probabilistic model of the network for granted [in my opinion].” In any case, though, it was an interesting talk, and I appreciated his passion for his project. He was confident, enough so that he even wanted to create a platform and token based on his work:
It was an informative and entertaining presentation, and he probably won over some people. Personally, it gave me an appreciation of the thriving competition for passionate ideas in this nascent community. More importantly, it showed me that there was an open-minded attitude here not often found elsewhere. Given that Casper has been the picked implementation for the next version of Ethereum, the organizers of DevCon could have shut out any dissenting opinions. Instead, though, they had embraced this alternate idea and had given Sirer a platform to advocate it. I now appreciated this whole movement on a grander scale.
Let’s hope that it will stand the test of time.
So, after wolfing down a lunch of Czech dumplings from the ample buffet and walking past the Giveth guy (who I didn’t know at the time and just thought was wearing a bad Halloween costume), I headed to the talk by Golem, out of curiosity since I had no idea who they were. Plus, since we were in Prague, it seemed appropriate. And after a few confused minutes, I finally got it. Wow.
Basically, Golem was offering a secure platform that decentralized the notion of buying and selling cycles of computing power. Instead of AWS EC2 and Azure VM, you could purchase your power from anonymous sources around the world. And on the other side of the coin, you could become an independent vendor, offering your computers as computing providers on the network. As a vendor, you’d just install their software on your machines. Of course, one would think of all the possible questions about trust on such a platform, but it seemed that Golem had those bases covered.
And how does Ethereum fit into all of this madness? It’s the transaction-based layer of the platform, of course! All agreements and purchases would occur within the Ethereum blockchain. How beautiful is that: one decentralized platform supporting another! After that lecture, I was hungry to discover what other projects were being developed with Ethereum in mind. So, where to next?!
So, the Ethereum conference this year lived up to its name of DevCon, unlike the “DeadCon” from last year. And the organizers couldn’t have picked a better city and better conference center for it!
Prague lived up to its reputation. What a view from the conference center!
And unlike last year, this year wasn’t about ICOs. It was about the developers again!
Talks and sessions about fundamentals was again back on the table. In fact, one could argue that there were too many options to choose from!
Even though I didn’t get to attend all of them, I did manage to sit for a few, which I’ll describe in subsequent posts. I’ll need the space just to summarize them!
So, after the last time with Redis, my team and I still felt uninformed about the features that Redis offers with its Enterprise version. And so, we were told that another session was coming up, one that would perhaps give us the answers we sought. Alas, that wasn’t really the case…but, hey, Redis definitely knows how to play the part of being a host. In my book, you get points for that.
This time, the event was held at Convene, which is uptown from Galvanize. In terms of accommodations, this hosting space was definitely one of the best that I’ve ever been to, especially in terms of food and a view:
And you have to appreciate any place that takes its coffee and yogurt seriously:
In the end, though, it seemed to be a similar presentation to the one a few months ago. We already knew about the HA functionality and regional synchronization that was available through the Enterprise version, but we were looking to possibly see it in action, along with the other bells and whistles. Oh well. Maybe next time…especially if it’s held again at Convene!