Michael Stonebraker wins Turing Award
newsoffice.mit.edu
newsoffice.mit.edu
And his students:
-Daniel Abadi (co-founder and Chief Scientist of Hadapt)
-Michael J. Carey (faculty at UC Irvine, formerly at U. Wisconsin Madison, NAE Member and ACM Fellow)
-Robert Epstein (founder and former VP of Engineering of Sybase)
-Diane Greene (co-founder and former CEO of VMWare)
-Paula Hawthorn (founder of Britton-Lee, formerly VP of Engineering of Informix)
-Marti Hearst (Professor at UC Berkeley)
-Gerald Held (former VP of Engineering of Oracle)
-Joseph M. Hellerstein (faculty at UC Berkeley)
-Anant Jhingran (VP and CTO for IBM's Information Management Division)
-Curt Kolovson (Sr. Staff Research Scientist at VMware)
-Clifford A. Lynch (executive director of the Coalition for Networked Information)
-Mike Olson (former CEO of Sleepycat Software and founding CEO of Cloudera)
-Margo Seltzer (Professor of Computer Science at Harvard, founder and former CTO of Sleepycat Software)
-Dale Skeen (founder of Tibco, founder and CEO of Vitria)
He worked on Aurora (http://homes.cs.washington.edu/~magda/aurora-medusa.pdf), which I don't think ever got a lot of commercial success, but was one of the earlier stream databases.
He also has some amazing work on non-traditional databases, for example he worked on H-store (http://hstore.cs.brown.edu/) which is now voltdb, which is an in-memory distributed database.
And then C-Store was the basis for Vertica: http://en.wikipedia.org/wiki/C-Store
I'm pretty sure Margo Seltzer (of BerkeleyDB fame) was his student at some point too.
Truly amazing researcher - and I think an example to those who focus on a teeny tiny minor niche their entire career and never explore anything else.
https://www.youtube.com/results?search_query=michael+stonebr...
Whoosh.
...
"Extaclty right, on a 35mm projector..."
hahaha
It opened my eyes to why traditional block-based RDBMS's were definitely going to go away and replaced by in-memory engines.
If you haven't read up on either VoltDB or SciDB or Stonebraker himself, I highly suggest you do, as it might make you think twice about some of your current setups. Here's a few quotes for the fun of it:
"I think the biggest NoSQL proponent of non-ACID has been historically a guy named Jeff Dean at Google, who’s responsible for, essentially, most to all of their database offerings. And he recently … wrote a system called Spanner,” Stonebraker explained. “Spanner is a pure ACID system. So Google is moving to ACID and I think the NoSQL market will move away from eventual consistency and toward ACID.”
“My prediction is that NoSQL will come to mean not yet SQL,”
"You saw that they went for Cassandra for inbox search and HBase for messaging. The reason they're not doing that on MySQL is that sharding MySQL is a lot of effort and you have to apply that effort to each new project."
That should be enough to get your curiosity piqued.
There are plenty of use cases where ACID compliance truly isn't needed.
Also, just because Google has one new database that features ACID compliance, does not mean that "Google is moving to ACID", it simply means that Google has identified a need for a portion of their data to be stored in an ACID compliant way.
[1] Proposed by Bayer and McCreight, and independently developed by Chiat and Schwartz, and also by Cole, Radcliffe and Kaufman, improved by many including D. Knuth.
[2] C-Store: A Column Oriented DBMS. Mike Stonebraker, Daniel Abadi, Adam Batkin, Xuedong Chen, Mitch Cherniack, Miguel Ferreira, Edmond Lau, Amerson Lin, Sam Madden, Elizabeth O'Neil, Pat O'Neil, Alex Rasin, Nga Tran and Stan Zdonik. VLDB, pages 553-564, 2005.
> An adjunct professor of computer science and engineering at MIT
Adjunct? Does this mean something different at MIT? Or is it some form of convenience for Stonebraker?
He's cashed out a number of successful businesses, so it's not likely that he needs money.
He's in his 70s. I would guess he still likes to teach and do research, but maybe not as a full-time professor.
Adjuncts don't have to go to committee meetings. :-)
Now it's more of a way to have 2/3 or more of the department work for unliveable wages which allows for an ever-growing administrative overhead in colleges while tuitions double every decade.
But, yeah, I hear from lots of sources that adjuncts making peanuts have become the rule rather than the exception in general US academia, and there's no disputing how administrators are taking over higher education, now even desiring to wrest little the faculty still control from them.
Education administration is a like a thorn stuck in my mind, they make _more_ than everyone else and for the most part only act as a gas to support their own structure.
It's hard to recognize when it starts, but you'll know it's happened once you see a lot of people who are not connected with the apparent goal of the machine, and there are posters all over the place touting whatever programs the administrators have created to justify their existence, as well as packaged training programs from motivational/educational consultants (think Franklin Covey).
The accretion or calcification model of bureaucratic formation is compelling, something like how a coral reef grows. The randomized surface provides eddies and pockets of protection for other life to flourish, RFPs and SBIRs can nestle in a protected arena with low local competition.
I just realized that large, messy codebases also follow the reef model of bureaucracy. Hadoop is like that coral reef, providing nooks and crannies for optimizations and integrations to take hold. I used to imagine Hadoop as Whale fall [0], but it is more of a mandlebulb. Had Hadoop not provided such a rich environment the secondary ecosystem wouldn't be as vibrant. Fail to Win?
I find management structures fascinating. Whenever I interact with one I probe it to see how much autonomy each individual in it has, what rules they can bend or not follow. Once the agents participating in the bureaucracy cannot bend the rules I think it will tend towards dystopia. Maybe 1984 isn't a warning against fascism, but the natural tendency of all bureaucracies to only support them selves.
[0] http://en.wikipedia.org/wiki/Whale_fall
note: I might sound like the stereo type of a hackernews-bitcoin-libertarian, but I assure you my politics are much more nuanced than that. I don't think that bureaucracy as a structure is bad, but it needs to be managed with something akin to the voting logic in a triple redundant control circuit [1] [2]. Most bureaucracies exist within a positive feedback loop, which rewards them for growth instead of efficiency. It is like getting paid by LOC instead of 1/LOC or 1/runtime.
[1] ftp://ftp.unicauca.edu.co/Facultades/FIET/DEIC/Materias/Instrumentacion%20Industrial/Instrument_Engineers__Handbook_-_Process_Measurement_and_Analysis/Instrument%20Engineers'%20Handbook%20-%20Process%20Measurement%20and%20Analysis/1083ch1_10.pdf
[2] http://ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/1985002...
Adjunct professors can also supervise research, which I believe is uncommon at other institutions.
[1] http://web.mit.edu/policies/2/2.3.html#sub2
[2] Four listed as "adjuncts" and four "professors of the practice", which are equivalent per [1]: https://www.eecs.mit.edu/people/faculty-advisors
[0] - http://www.se-radio.net/2013/12/episode-199-michael-stonebra...
http://www.softwarememories.com/2007/01/21/why-michael-stone... http://www.dbms2.com/category/michael-stonebraker/
www.tamr.com
Google cache in case you have trouble reaching the website (apparently under some understandably heavy load).
See discussion and comment from Adam Sah at http://radar.oreilly.com/2008/11/the-commoditization-of-mass... for more context for column-storage and log analysis.
edit: link to article.
Mike was my thesis advisor at Cal, and had enormous influence on all sorts of things beyond databases, including (I believe) the founding of the CS department and the negotiation of how Ingres technology spin off from Cal (which owns the IP), which became the prototype for how others would create companies like Inktomi and many more.
Article text: http://pastebin.com/MTdagueN
https://en.wikipedia.org/wiki/Ingres_%28database%29
https://en.wikipedia.org/wiki/Illustra
http://www.v3.co.uk/v3-uk/analysis/1943302/disparate-databas...
https://en.wikipedia.org/wiki/StreamBase_Systems
https://en.wikipedia.org/wiki/Vertica
https://en.wikipedia.org/wiki/VoltDB
http://cs.brown.edu/research/aurora/
https://en.wikipedia.org/wiki/C-Store
https://en.wikipedia.org/wiki/H-Store
http://publications.csail.mit.edu/abstracts/abstracts07/ston...
If you're talking about actually implementing a full transactional database system, strong foundational books are:
Transaction Processing: Concepts and Techniques (Gray and Reuter)
Transactional Information Systems: Theory, Algorithms, and the Practice of Concurrency Control and Recovery (Vossen and Weikum)
Neither are exactly easy reading, but the concepts therein are really important.
Also if you are interested in B-Trees start with "The Ubiquitous B-Tree" by Comer. [ http://dx.doi.org/10.1145/356770.356776 ].
http://www.acm.org/press-room/news-releases/2015/turing-awar...
(among other things I was part of one of the first early adopter teams that used his Streambase product, while at Orbitz.)