Top Banner
SQL gabriele lana [email protected] twitter: @gabrielelana http://joind.in/2938
40

Nosql

Jan 15, 2015

Download

Technology

Gabriele Lana

Keynote for the italian nosql day, I have tried to explain the meaning of the word "nosql" through an historical path
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 2: Nosql

I’am going to tell you what

is this

thing...

SQL

Page 3: Nosql

SQLis not aboutrejecting

sql/relationaldatabases

Page 4: Nosql

SQLis not aboutembracingnon sql/

non relationaldatabases

Page 5: Nosql

then what is this all about?

let me tell you a story...

Page 6: Nosql

Hype cycle of technologyVisib

ility

maturity

technologytrigger

peak ofinflated

expectation

disillusionment

productivity

obsolescence

Page 7: Nosql

Visib

ility

maturity

technologytrigger

disillusionmentleads to

Hype cycle of technology

Page 8: Nosql

Visib

ility

maturity

but sometimes they come back

Page 9: Nosql

Visib

ility

maturity

volume => longevity (legacy)

Page 10: Nosql

new ideasare made ofold ideasapplied in

a differentcontext

Page 11: Nosql

an example

Page 12: Nosql

an example

Page 13: Nosql

an example

Page 14: Nosql

an example

???probably

somethingin between

Page 15: Nosql

All of this has happened before, and it will all happen

again...

Page 16: Nosql

ok, but this is the

nosql day!what are

you trying to say?

we should start from the beginning...

Page 17: Nosql

ui

busin

ess

storag

e• single user• data owned by applications• custom solution

dbms: the beginning

Page 18: Nosql

ui

busin

ess

storag

e

• every applications needs to develop his own solution...

dbms: the beginning

Page 19: Nosql

ui

busin

ess

lib

rary

• more robust solution

dbms: first libraries

Page 20: Nosql

FirstNode.SecondNode.attribute

FirstNodeat

trib

ute

SecondNode

attr

ibut

e

dbms: first libraries(navigational databases)

Page 21: Nosql

dbms: first libraries(navigational databases)

FirstNode.SecondNode.attribute

FirstNodeat

trib

ute

SecondNode

attr

ibut

e

• cobol: banking• m/mumps: health care

Page 22: Nosql

dbms: first libraries(key value databases)

RecordKey

attr

ibut

eRecordKey

attr

ibut

e

RecordKey

attr

ibut

e

RecordKey

attr

ibut

e

Page 23: Nosql

dbms: first libraries(key value databases)

RecordKey

attr

ibut

eRecordKey

attr

ibut

e

RecordKey

attr

ibut

e

• dbm: ken thompson-> QDBM-> tokyo cabinet

Page 24: Nosql
Page 25: Nosql

dbms: relational model

rdbms

business

network

application

application

application

• system-r• ingres -> postgres

• sybase• informix

Page 26: Nosql

dbms: relational model

rdbms

business

network

application

application

application

duplicated business logic

who is the data’s owner?

Page 27: Nosql

-

(mrtg/rrd)

rela

tional

navigational

tim

e

object.

oriented

network

key ->

value

(ldap

/ad)docum

ent

.

orie

nted

colum

n

orient

ed

Page 28: Nosql

dbms: relational server

rd

bm

s

application

application

application

busin

ess

• consistency• security• integrity• validity

Page 29: Nosql

dbms: relational server

rd

bm

s

application

application

application

busin

ess

relational model as a (declaratively) programmable business logic

rise the data driven design

Page 30: Nosql

impedance mismatch

Page 31: Nosql

cost o

f im

plem

entatio

n

context

purpose

Page 32: Nosql

dbms: relational model

rdbms

business

network

application

application

application

duplicated business logic

who is the data’s owner?

Page 33: Nosql

dbms: service oriented

application

application

application

network

Page 34: Nosql

dbms: service oriented

application

application

network

ROA: an architectural style where applications are responsible to deliver a service to the network (aka users and other applications)

Page 35: Nosql

SQLis not aboutrejecting

sql/relationaldatabases

Page 36: Nosql

SQLis about

rejectingthe notion

that there isone true and

centralized wayto store anykind of data

Page 37: Nosql

what about the future?

storagefor morespecific

data

Page 38: Nosql

what about the future?

knowledgeextraction

Page 39: Nosql

what about the future?

“REAL”relationaldatabases

Page 40: Nosql

Questions?