Skip to content
0:00 / 0:00

#michaelstonebraker#bigdata#nosql

Michael Stonebraker | Big Data is (at least) Four Different Problems

Michigan Engineering

64K subscribers • 1 video on Hallway

YouTube
  • Recommended by 5 people: 5 on Hacker News.
  • A classic. People kept recommending it from 2015 to 2024.
  • Presented by Michael Stonebraker, Turing Award winner
  • An opinion. It argues one side of a question engineers disagree on.

Intermediate. Assumes working knowledge.

29K views10 years ago5 recommendations

Databases and dataDistributed systemsDatabase internalsSQLNoSQL and document databases

Michael Stonebraker explains that big data consists of four distinct challenges—volume, velocity, variety, and big analytics—and critiques NoSQL solutions.

Big Data is (at least) Four Different Problems Michael Stonebraker, Co-Director, Intel Science & Technology Center, MIT Special Lecture Series: William Gould Dow Distinguished Lectureship Sponsoring Department: EECS eecs.umich.edu/ "Big Data" means different things to different people. To me, it means one of four totally different problems: Big volumes of data, but "small" analytics. The traditional data warehouse vendors support SQL analytics on very large volumes of data. In this talk, I make a few comments on where I see this market going. Big analytics on big volumes of data. By big analytics, I mean data clustering, regressions, machine learning, and other much more complex analytics on very large amounts of data. I will explain the various approaches to integrating complex analytics into DBMSs, and discuss which ones seem more promising. In addition, I will explore why Hadoop, in its current form, will not be a player in this market. Big velocity. By this I mean being able to absorb and process a firehose of incoming data for applications like electronic trading. In this market, the traditional SQL vendors are a non-starter. I will discuss alternatives including complex event processing (CEP), NoSQL and NewSQL systems. I will also make a few comments about the "Internet of Things." Big Diversity. Many enterprises are faced with integrating a larger and larger number of data sources with diverse data (spreadsheets, web sources, XML, traditional DBMSs). The traditional ETL products do not appear up to the challenges of this new world, and I talk about an alternate way to go. About the Speaker: Michael Stonebraker (MS 1966, PhD 1971) has been a pioneer of database research and technology for more than a quarter of a century. He was the main architect of the INGRES relational DBMS, and the object-relational DBMS, POSTGRES. These prototypes were developed at the University of California at Berkeley where Stonebraker was a Professor of Computer Science for twenty five years. More recently at MIT, he was a co-architect of the Aurora/Borealis stream processing engine, the C-Store column-oriented DBMS, the H-Store transaction processing engine, the SciDB array DBMS, and the Data Tamer data curation system. He presently serves as Chief Technology Officer of Paradigm4 and Tamr, Inc. Stonebraker was awarded the ACM System Software Award in 1992 for his work on INGRES. Additionally, he was awarded the first annual SIGMOD Innovation award in 1994, and was elected to the National Academy of Engineering in 1997. He was awarded the IEEE John Von Neumann award in 2005, and the ACM AM Turing Award - the "Nobel Prize of computing" in 2014. He is presently an Adjunct Professor of Computer Science at MIT, where he is co-director of the Intel Science and Technology Center focused on big data. Speaker Website: csail.mit.edu/user/1547

Why it's here

5 people recommend this

What people say. Highly recommended by database engineers as a foundational critique of NoSQL hype and a clear breakdown of database architectures.

edejongon Hacker News • Recommends

On “The Marketing Behind MongoDB”

Whenever I see a young gullible engineer, all twinkly-eyed and bedazzled by the MongoDB hype (or any other NoSQL hype), I'll send him a link 1 on a rather interesting talk by a very thoughtful Turing award winning engineer named Michael Stonebraker. It takes a couple of days for the charm of NoSQL to wane off, but eventually they'll always see how they have been fooled into believing without a sane level of critique. 1 link to this video

vishnuguptaon Hacker News • Recommends

On “Big data is dead (2023)”

I first heard of this 3 V's in a Michael Stonebreaker's talk1. For the uninitiated he's a legend in DBMS space, Turing award winner2. Highly recommend this and related talks by him, most of them are in YouTube. 1 link to this video 2 link

mattsteon Hacker News • Recommends

On “Readings in Database Systems, 5th Edition”

Stonebraker recently gave a talk at my school on where he thinks databases are headed in the future0. Definitely worth a watch. 0 link to this video

jasodeon Hacker News • Recommends

On “Urban Myths about SQL (2015)”

…e/MSSQL.) ++ He believes in ACID ++ He believes that other db engines' (NoSQL, etc) approaches to gain speed and scaling of clusters by sacrificing SQL and ACID is wrong and his proof is that those other products end up eventually bolting on SQL and ACID anyway. I think a better presentation to flesh out these ideas is the following youtube video: link to this video It's 55 minutes long so to save time, HN readers may prefer to browse it by pressing "L" key to step through it quickly. Just read the slides shown behind him and if the bullet points look interesting, rewind and listen to his presentation. One can dwell on those SQL/ACID merits in isolation and consider separately, the question of whether…

wencon Hacker News • Recommends

On “Making Databases Work: The Pragmatic Wisdom of Michael Stonebraker (2018)”

I read the Red Book when I was figuring out data architectures for my company. (the other book was Designing Data-Intensive Archictures by Martin Kleppmann) Stonebraker et al are very opinionated (especially about SQL and relational databases), but in a way I can accept because a lot of his thinking is based on first-principles. Stonebraker also has a string of database successes (Ingres, Postgres, Vertica etc.) which gives him enough street cred to prove he's not just spewing theory from an ivory tower. He's not necessarily correct in every opinion, but his opinions are interesting and worth considering. I enjoyed his talk on "Why Big Data is at least 4 different problems" link to this video

elvinyungon Hacker News • Mentions

On ““Follow-The-Workload” Beats the Latency-Survivability Tradeoff in CockroachDB”

Whether that actually matters is arguable: No one has performant distributed (i.e. cross-partition) ACID. (Except maybe Google.) For the thing that does matter, which is ACID within the same partition/entity group, I would argue that RethinkDB already does have that. Mike Stonebraker says that there are no fast distributed transactions 1. I'm inclined to believe him, and that's not just an appeal to authority. 1 link to this video

refseton Hacker News • Mentions

On “Fast Analytics and Graph Traversals with Datalog”

Firstly, disclosure: I work on XTDB, where we are in the process of building out a new columnar SQL engine that also (still) supports edn-flavoured Datalog, see link Perhaps the most fundamental aspect here is the inherent tension between (A) typical columnar relational schemas which primarily target efficient OLAP across very wide & sparse tables, and (B) the nature of 'graph' systems (whether OLAP or OLTP) which tend towards handling a huge number of tables and/or recursive self-joins + incremental view maintenance. I believe Michael Stonebraker's conjecture continues to be that a "one size fits all" database engine is essentially unachievable, and therefore you can't expect a single dat…