One Size Doesn't Fit All: What's wrong with my database?
10
One Size Doesn’t Fit All February 22, 2012 Mark R. Madsen http://ThirdNature.net
-
Upload
mark-madsen -
Category
Technology
-
view
109 -
download
1
description
Slides from webcast on changes in the database market, basics of what's wrong with a relational database, where the market is headed. Video replay is available at https://bloorgroup.webex.com/bloorgroup/lsr.php?AT=pb&SP=EC&rID=4848212&rKey=ca069779655c1fe0
Transcript of One Size Doesn't Fit All: What's wrong with my database?
One Size Doesn’t Fit All
February 22, 2012
Mark R. Madsenhttp://ThirdNature.net
Presenter
Presentation Notes
One size never fits all. We just pretend it does because it’s a useful fiction. The goal of this talk is three-fold: To explain the underlying dynamics of the market that supplies the technologies and architectures we use in our work To provide an explanation that helps frame the problems we have to solve so we can think better about them To put some of the “big data” impact into context Image: public domain
The future of data is the database
Presenter
Presentation Notes
So let’s start talking about the main point of this talk. Big data and technology. Conceptual model. This data vs that data.
You keep using that word. I do not think it means what you think it means.
Presenter
Presentation Notes
What do you mean by database? We stopped using “relational” to save on syllables. We probably do mean relational, because when it comes to data we have to find ways to relate it. The conceptual framework is valid. The specific implementations are not so much. Everyone confuses the relational database with either a specific relational database, like mysql sucks therefore everything sucks, or
The relational database is the franchise technology for storing and retrieving data, but…
1. Global, static schema model
2. No rich typing system
3. Many are not a good fit for network parallel computing, aka cloud
4. Limited API in atomic SQL statement syntax & simple result set return
5. Poor developer support
Good conceptual model, but a prematurely standardized implementation
Presenter
Presentation Notes
Being a franchise player doesn’t mean remaining a franchise player. Also: the evolution from what it was: support for transactions. Queries came later. Good at the time, it took a while for both hardware and software to catch up with the needs. The unprecedented growth of data isn’t really because our memories are short. 1990 explosion of data capture made it harder.
Plus, if they’re all the same why are there so many?
Sybase IQ, ASETeradata, Aster DataOracle, RACMicrosoft SQLServer, PDWIBM DB2s, NetezzaParaccelKognitioEMC/GreenplumOracle ExadataSAP HANAInfobrightMySQLMarkLogicTokyo Cabinet
EnterpriseDBLucidDBVectorwiseMonetDBExasolIlluminateVerticaInfiniDB1010 DataSANDEndecaXtreme DataIMSHive
AlgebraixIntersystems CachéStreambaseSQLStreamCoral8IngresPostgresCassandraCouchDBMongoHbaseRedisRainStorScalaris
And a few hundred more.
Presenter
Presentation Notes
This is why our job is hard, even though a great many products are “also ran” in the market, they are still in business and competing for attention. People smell money, and when that happens in tech, startups and rebadgings appear.
The future of data is the relational database?
SQL noSQL
Presenter
Presentation Notes
The main point: bottom up, top down, taxonomy, ontology. This data vs that data, where we are today. Mrogati point: Exploration vs exploitation. The fixity of the database is a big obstacle to analysis because it fixes a context/one interpretation of the information. It’s hard to change that once it’s in place, yet context changes. The context changes as the data is used because data is used to take actions which many times change the environment. But with a DB it’s hard to change as new understanding or as context changes. Linnaeus to Buffon, Dewey to Cutter is just like SQL to nosql, relational to information retrieval, schema to list, apriori to emergent. Like taxonomy in the EU, and suddenly the new world gets added. It’s an explosion in both volume and variety. NoSQL solves the top down, authority driven, bureaucratic, controlling, hierarchical, static problems.
The future of data is the relational database?
SQL noSQL
Presenter
Presentation Notes
This data becomes that data, at which point there’s new data, and that data is easy to deal with. Your choices land you in paradise or purgatory. Don’t pick prematurely, Reality is that both have their place, solve different problems. By freeing information from it’s physical form (the place, form description/debate) you can actually do both, for the first time in history, technology caught up and then surpassed the ideas.
Technologies are not perfect replacements for one another.
When replacing the old with the new (or ignoring the new over the old) you always make tradeoffs, and usually you won’t see them for a long time.
About Third Nature
Third Nature is a research and consulting firm focused on new and emerging technology and practices in analytics, business intelligence, and performance management. If your question is related to data, analytics, information strategy and technology infrastructure then you‘re at the right place.
Our goal is to help companies take advantage of information-driven management practices and applications. We offer education, consulting and research services to support business and IT organizations as well as technology vendors.
We fill the gap between what the industry analyst firms cover and what IT needs. We specialize in product and technology analysis, so we look at emerging technologies and markets, evaluating technology and hw it is applied rather than vendor market positions.
About the PresenterMark Madsen is president of Third Nature, a technology research and consulting firm focused on business intelligence, analytics and information management. Mark is an award-winning author, architect and former CTO whose work has been featured in numerous industry publications. During his career Mark received awards from the American Productivity & Quality Center, TDWI, Computerworld and the Smithsonian Institute. He is an international speaker, contributing editor at Intelligent Enterprise, and manages the open source channel at the Business Intelligence Network. For more information or to contact Mark, visit http://ThirdNature.net.
