The NoSQL movement @ DotNetToscana
Upcoming SlideShare
Loading in...5
×
 

The NoSQL movement @ DotNetToscana

on

  • 786 views

 

Statistics

Views

Total Views
786
Views on SlideShare
786
Embed Views
0

Actions

Likes
1
Downloads
14
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    The NoSQL movement @ DotNetToscana The NoSQL movement @ DotNetToscana Presentation Transcript

    • Matteo Baglini www.dotnettoscana.orgSoftware Developer, Freelancematteo.baglini@gmail.comhttp://it.linkedin.com/in/matteobaglinihttp://github.cpom/bmatte
    • No more SQL, awesome!!! 2
    • Yes but, why? 3
    • Modern Web ApplicationRequirements 4
    • High number of heterogeneous content 5
    • Many connected users 6
    • Immediately push info to the users 7
    • Collection of large data sets 8
    • Scalable and on-demand architecture 9
    • Dynamic requirements 10
    • RDBMS 11
    •  Tables and relations Schema-full Pre-defined structure Transaction (even Distributed) Consistency Declarative query language (SQL) 12
    • Is it the right tool? 13
    • Alternative Database (NoSql) 14
    •  Alternative structures Schema-free Non transactional Eventual consistency Programmatically query routine Easy to scale-out Use case oriented 15
    • NoSqlCategories 16
    •  Data (Value) was identified by a unique Key The Value can be anything Primarly queriable by Key Examples: Amazon SimpleDB, Azure Table Storage, Riak, Redis, Voldemort, MemcacheDB. 17
    •  Data contained into Documents that was identified by a unique Key Document was stored as JSON object (properties and values) Values can be scalars, arrays or complex types Queriable by Key or MapReduce Examples: MongoDB, CouchDB, RavenDB 18
    •  Data contained into Tables and Column Families Each Column Families was a set of key-value pairs Partial schema Queriable by Key, MapReduce or custom langs Examples: Google BigTable, Hbase, Cassandra 19
    •  Data contained into Nodes and Edges Each Node was a set of key- value pairs Each Edge represent a relationship Queriable by custom langs Examples: Neo4j, OrientDB, Titan, Sones 20
    • NoSql orRDBMS ? 21
    • PolyglotPersistence 22