38
Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective

Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective

Embed Size (px)

Citation preview

Page 1: Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective

Postgresql East 2010

Philadephia, PA

Databases – A Historical Perspective

Page 2: Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective

WHO AM I?

Brent FriedmanSenior Solutions Consultant

Cincom Systems, [email protected]

Databases – A Historical Perspective

Page 3: Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective

What is a database?

Databases – A Historical Perspective

Page 4: Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective

The earliest computers weren’t sufficiently complex to entertain the idea of a free-standing database. Data was directly linked with the application in memory at the time.

Databases – A Historical Perspective

TIMELINE: 1950s

Page 5: Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective

DATABASE – NETWORK MODEL

CODASYL

References to data are through low-level pointers. Adding or changing a database required considerable reworking of the storage mechanism.

Databases – A Historical Perspective

TIMELINE: 1960s

Page 6: Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective

DATABASE – HIERARCHICAL MODEL

IBM’s IMS

These databases allow only 1:1 or 1:many relationships. Such databases can be incredibly fast, but are not well suited to hold disparate types of information.

Databases – A Historical Perspective

TIMELINE: 1960s

Page 7: Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective

Name a hierarchical database system that is still in everyday use around the world.

Hint: What contact information about people do YOU store right now?

Databases – A Historical Perspective

DATABASE TRIVIA

Page 8: Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective

Around 1964, the term "data base" was "coined by workers in military information systems to denote collections of data shared by end-users of time sharing computer systems." In earlier days, each application had its own "master files" of data, so the concept of a data collection that could be shared by multiple applications was a new idea in efficiency.

http://www.snee.com/bobdc.blog/2005/12/25-years-of-database-history-s-1.html

Databases – A Historical Perspective

Page 9: Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective

TIMELINE: 1964

Databases – A Historical Perspective

http://www.computersciencelab.com/ComputerHistory/HistoryPt4.htm

Page 10: Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective

TIMELINE: 1967

Databases – A Historical Perspective

The term “memory bank” enters, and soon (thankfully) leaves, the English language.

Page 11: Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective

1969…

Was not just about the counter-culture. But things

were about to happen…

Databases – A Historical Perspective

Page 12: Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective

TIMELINE: 1970

Edgar F. Codd, commonly cited as E. F. Codd, published a paper on something he called “Relational Database Theory”

Databases – A Historical Perspective

http://www.ibiblio.org/jelkner/IntroToIT/database_lesson.html

Page 13: Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective

Codd, continued

Codd’s revolutionary idea did not focus on the relational algebra, but rather on how

the data should be addressed. His theory separated the schema from the storage

mechanism.

Databases – A Historical Perspective

Page 14: Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective

RDBMS – What’s that?

A relational database management system is ultimately based on E. F.

Codd’s theories.

Databases – A Historical Perspective

Page 15: Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective

TIMELINE – 1970sRDBMS – Path 1

The Ingres Group:Ingres; Sybase; MS Sql Server; and

something called Postgres…

These used the QUEL language

Databases – A Historical Perspective

Page 16: Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective

TIMELINE – 1970sRDBMS – Path 2

The (IBM) System R Group:DB2; Oracle; Nonstop SQL

These used the SQL language

Databases – A Historical Perspective

Page 17: Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective

TIMELINE - 1976

Peter Chen proposed the Entity-Relationship diagram

(ERD), which is still sometimes called a “Chen

diagram”

Databases – A Historical Perspective

Page 18: Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective

ERD – Chen Diagram

http://en.wikipedia.org/wiki/Entity-relationship_model

Databases – A Historical Perspective

Page 19: Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective

ERDs and so on

There are a multitude of design practices, modelling

tools, and even variations on how to diagram relational

data.

Databases – A Historical Perspective

Page 20: Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective

To avoid tomato throwing, insinuations about lineage,

and general bodily harm, we will avoid a direct discussion of specific schools of thought in the area of relational data

representation.

Databases – A Historical Perspective

Page 21: Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective

If you really need a hint…

Database Design Studio

Lite or Pro versions

www.chillisource.com

Databases – A Historical Perspective

http://www.thespeciousreport.com/2006/06060222comedy.html

database design tool

Page 22: Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective

TIMELINE – 1980s

The QUEL branch of RDBMS suffers a horrible boating accident, and is not heard

from again.

Databases – A Historical Perspective

Page 23: Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective

TIMELINE – 1980s

SQLStructured Query Language

becomes the de facto standard among all relational

database products.

Databases – A Historical Perspective

Page 24: Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective

SQL – The Real Image

Databases – A Historical Perspective

Page 25: Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective

TIMELINE – mid 1980s

The rise of the personal computer (PC) issues in a host

of new ‘personal’ relational databases:

Paradox; Dbase III; RBASE; etc.

Databases – A Historical Perspective

Page 26: Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective

TIMELINE – early 1990s

The trend toward 4GL (4th generation languages) leads

to visual front-ends for personal databases:Powerbuilder; Oracle

Developer;and even early MS VB

Databases – A Historical Perspective

Page 27: Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective

TIMELINE - 1990

Some geek named Tim Berners-Lee, or “Sir Timothy John Berners-Lee, OM, KBE,

FRS, FREng, FRSA” for all you Brits, proposed mating

hypertext with the early Internet.

Databases – A Historical Perspective

Page 28: Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective

TIMELINE – mid 1990s

This “World Wide Web” thing really catches on, once Al

Gore let everybody know they could do something with their

dial-up modems besides playing DECWar at the local

university.

Databases – A Historical Perspective

Page 29: Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective

TIMELINE – late 1990s

Relational databases become so ubiquitous that even your mother knows what “DBA”

means.

Databases – A Historical Perspective

Page 30: Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective

TIMELINE – 1995ish

Graduate students Andrew Yu and Jolly Chen revise

Postgres’s query language, POSTQUEL, to use SQL, and

call it Postgres95…

http://www.postgresql.org/about/history

Databases – A Historical Perspective

Page 31: Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective

TIMELINE – 2000s

Object databases, although they have been around for a while, start to get noticed by

non-geeks.

Databases – A Historical Perspective

Page 32: Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective

The role of object databases in “SKYNET” has not yet been

determined…

Databases – A Historical Perspective

Page 33: Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective

TIMELINE – 2005

Columnar databases find a growing audience in the “need for speed” crowd.

While probably still a niche segment, products such as

Monet are increasing in popularity.

Databases – A Historical Perspective

Page 34: Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective

TIMELINE -2008

Sun Microsystems acquires MySQL

Databases – A Historical Perspective

Page 35: Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective

TIMELINE – 2009

The rise of distributed systems inspires the NoSQL movement – rejection of traditional RDBMS systems for distributed data structures, such as Apache

Hadoop

Databases – A Historical Perspective

Page 36: Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective

TIMELINE – 2010

Will cloud computing gain ground on traditional IT infrastructure

models?

Databases – A Historical Perspective

Page 37: Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective

Questions?

Comments?

Databases – A Historical Perspective

Page 38: Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective

END OF

PART ONE

Databases – A Historical Perspective