How do we consume and make sense of all this data? with Don Haderle

At one time not long ago IT departments thought they could control the information model within the enterprise thus ensuring wonderfully accurate information. Unfortunately the world moved too fast and the high value information outside the enterprise exploded even more quickly than the data within the enterprise which was already overwhelming. The consequence of this is that the basic data architecture for an enterprise today is a Federation of information (versus a single monolithic repository) with strong reconciliation to acknowledge the disconnects between the various information sets both within and outside the enterprise. So how do we deal with all of this data and organize the information so it makes sense?

First generation databases (1960s) dealt with a single application use of information in a very strict form (hierarchical, network).

Second generation databases (late 1970s-1990s) dealt with a set of applications sharing the same data which was encoded in a very strict form (relational).

Third generation databases (late 1990s to present: nosql/newsql) deal with multiple applications sharing data that is in a very dynamic form (schemaless is actually dynamic schema) with very elastic needs (expansion of data models (new data/information types), expansion/contraction of performance characteristics). Third generation databases deal with capture of this dynamic data and the federation of information from myriad data sources inside and outside the enterprise. They are the fabric of the federated information architecture.

A simple data point: Smartphone traffic in 2012 was 885 petabytes per month - a 70% growth rate year to year. There is a need to analyze this in real-time, integrated with social media, structured data, and more to satisfy many business opportunities. Within this set of data, the information models (data packet descriptions) increased 10-100fold. We see similar trends in medical, gaming, scientific, and myriad other sectors.

We'll discuss NOSQL/NEWSQL databases; how they basically differ, and what roles they play.

Savory snacks, gourmet cookies and tasteful beer, wine and non-alcoholic beverages provided.

About Don Haderle:

Don Haderle served as Vice President and Chief Technology Officer for the Information Management segment of IBM for 14 years. He joined IBM in 1968 as a Software Developer, and eventually rose to lead the technical team that created IBM’s premier relational database management system, DB2, from 1970 to 1990. From 1968 to 2005, Don Haderle served in Research & Development at IBM Corp. He retired from IBM in 2005.

Don Haderle is known as the “Father of DB2.” He was appointed IBM Fellow in 1989, appointed Association for Computer Machinery (ACM) Fellow in 2000 in recognition of his impact on database technology, and elected to the National Academy of Engineering for contributions to the management of high-performance relational databases and leadership in founding the relational database management industry.

Don Haderle serves on the Technical Advisory Board at Boardwalktech and Palamida, and advises LTS Commerce. He has also served as a Member of the Technical Advisory Board at Vertica Systems, Inc., Interlace Systems Inc., Ants Software Inc., and newScale Inc. He secured more than 50 patents and disclosures across all areas of database management, and led the efforts to create and deploy the technology in the market. He consults with VCs, startups, and a few mature businesses. Don Haderle is a pioneer of relational database and information management technology. Don is a graduate of UC Berkeley, with a Bachelor of Arts degree in Economics in 1967.