Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
NoSQL Directions
Max Schireson
CEO, 10gen
@mschireson
max@10gen.com
2
Me
•  Almost 20 years in databases
–  9 years at Oracle
–  7 years at MarkLogic
–  3 years at 10gen
•  As old as the rel...
3
Today’s discussion
•  State of the industry and direction for the industry
–  Not a laundry list of features needed
–  N...
4
540 Million years ago
5
Biological vs technological evolution
•  Same
–  Innovations succeed or fail based on surrounding conditions
–  Changes ...
6
1970
7
Human/computer interaction, 1970
8
2003
9
Now
10
Soon?
11
Changes in Application Development
Then Now
Data Tabular Everything
Development Waterfall Iterative
Deployment Data Cen...
12
Using old tools for new jobs
•  Avoid the database – caches
•  Denormalization
•  ORMs
•  Manual sharding
•  Complexity...
13
Is this really the right way?
14
Time to question
•  Do I want a database
•  HW vs software
•  Data model
•  Deployment model
•  Disk vs memory
•  Consi...
15
Thus NoSQL was born…
•  All NoSQL have in common
–  Different data model
–  Distributed architecture
•  Most NoSQL have...
16
…and grew rapidly
17
Visible web companies using NoSQL
•  Google (bigtable)
•  Amazon (dynamo)
•  Netflix
•  Shutterfly
•  EBay
18
… plus some visible enterprise users
•  Metlife
•  Goldman Sachs
•  Telefonica
•  UK Government digital service
19
MetLife
20
Big players are joining the party
21
Some competition from big players
22
Some competition from big players
23
Lots of work to do before we can win
•  Security
•  Managability
•  Integrations
•  Market fragmentation
•  Skill base,...
24
Two distinct challenges
•  Making it better
•  Making it accessible
25
The rules matter
26
Two possible futures
27
Two possible futures
28
The difference: customer success
29
Success for NoSQL is a team effort
•  Vendors
–  Invest aggressively in product – better and more accessible
–  Value u...
30
Success for NoSQL is a team effort
•  Users
–  Use the right tool for the right job
–  Think strategically about insert...
31
Challenges in working together
•  Bad news:
–  History of win/lose vendor negotiations
–  Product selection -> vendor c...
32
Success for NoSQL is a team effort
•  Together
–  Transition a major part of the stack to open source
–  Remake the ven...
NoSQL Directions Keynote from NoSQL Now 2013
Upcoming SlideShare
Loading in …5
×

NoSQL Directions Keynote from NoSQL Now 2013

834 views

Published on

The NoSQL marketplace is undergoing a rapid transition – from community-driven development and niche deployments to rising enterprise adoption and voice in the mainstream. In this talk, Max discusses differences among NoSQLtechnologies, trends in NoSQL impacting the enterprise, and how NoSQL is shaping the overall data management landscape. He will also outline lessons from early NoSQL adopters and how these can be instructive for would-beNoSQL adopters, both from a technological and organizational standpoint.
Whether you are already using NoSQL technologies or considering new projects, come learn how you can be a part of the greatest change in the data management industry in over 30 years.

Published in: Technology
  • Be the first to comment

NoSQL Directions Keynote from NoSQL Now 2013

  1. 1. NoSQL Directions Max Schireson CEO, 10gen @mschireson max@10gen.com
  2. 2. 2 Me •  Almost 20 years in databases –  9 years at Oracle –  7 years at MarkLogic –  3 years at 10gen •  As old as the relational database (born in 1970) •  Geek turned businessperson
  3. 3. 3 Today’s discussion •  State of the industry and direction for the industry –  Not a laundry list of features needed –  Not an advertisement for one NoSQL product over another •  The past – why change is needed •  The present – NoSQL successes and shortcomings •  Some possible futures •  Charting our course together
  4. 4. 4 540 Million years ago
  5. 5. 5 Biological vs technological evolution •  Same –  Innovations succeed or fail based on surrounding conditions –  Changes in environment can reset complex ecosystems –  Equilibrium is a complex interplay of many components •  Different –  Biological changes introduced at a largely fixed rate –  Technological changes introduced at a variable rate
  6. 6. 6 1970
  7. 7. 7 Human/computer interaction, 1970
  8. 8. 8 2003
  9. 9. 9 Now
  10. 10. 10 Soon?
  11. 11. 11 Changes in Application Development Then Now Data Tabular Everything Development Waterfall Iterative Deployment Data Center Cloud Consumption PC Mobile Decisions CIO Developers
  12. 12. 12 Using old tools for new jobs •  Avoid the database – caches •  Denormalization •  ORMs •  Manual sharding •  Complexity •  Rigidity •  Data silos
  13. 13. 13 Is this really the right way?
  14. 14. 14 Time to question •  Do I want a database •  HW vs software •  Data model •  Deployment model •  Disk vs memory •  Consistency model
  15. 15. 15 Thus NoSQL was born… •  All NoSQL have in common –  Different data model –  Distributed architecture •  Most NoSQL have in common –  Open source –  Some rethink of transactions –  Some form of new query language
  16. 16. 16 …and grew rapidly
  17. 17. 17 Visible web companies using NoSQL •  Google (bigtable) •  Amazon (dynamo) •  Netflix •  Shutterfly •  EBay
  18. 18. 18 … plus some visible enterprise users •  Metlife •  Goldman Sachs •  Telefonica •  UK Government digital service
  19. 19. 19 MetLife
  20. 20. 20 Big players are joining the party
  21. 21. 21 Some competition from big players
  22. 22. 22 Some competition from big players
  23. 23. 23 Lots of work to do before we can win •  Security •  Managability •  Integrations •  Market fragmentation •  Skill base, intellectual framework •  Maturity
  24. 24. 24 Two distinct challenges •  Making it better •  Making it accessible
  25. 25. 25 The rules matter
  26. 26. 26 Two possible futures
  27. 27. 27 Two possible futures
  28. 28. 28 The difference: customer success
  29. 29. 29 Success for NoSQL is a team effort •  Vendors –  Invest aggressively in product – better and more accessible –  Value user success over monetization –  Be true to the essence of what you have –  Build an ecosystem to complement your product
  30. 30. 30 Success for NoSQL is a team effort •  Users –  Use the right tool for the right job –  Think strategically about insertion strategy –  Invest in training your team –  Don’t hesitate to ask for help
  31. 31. 31 Challenges in working together •  Bad news: –  History of win/lose vendor negotiations –  Product selection -> vendor captivity –  Captivity -> fear -> withdrawl •  Opportunity: –  Open source: customers have more power –  Vendors earn their business every year –  Low prices, high value -> alignment around success
  32. 32. 32 Success for NoSQL is a team effort •  Together –  Transition a major part of the stack to open source –  Remake the vendor/client relationship –  Reinvent the database industry –  Rejuvenate IT’s relationship with the business –  Revolutionize application development

×