RavenDB

Why I stopped worrying and learned to embrace NoSQL

Transcript

1. RavenDB Or “Why I stopped worrying and learned to embrace NoSQL”
2. Advanced Notice This presentation should not be considered gospel, nor should you throw away everything you know about RDBMS. This is just another weapon in your armoury to solve problems.
3. History – Membership App Why there is a need for document databases - a database in a database in a database in a database
4. Relational Databases • Management Information Systems • High Performance • Well structured information • Data integrity
5. NoSQL Don’t be afraid
6. NoSQL • Not Only SQL • No Schema • High Performance • Key-Value Stores • Open Source • Scalable
7. Differences
8. SQL Database Differences { "AlbumArtUrl": "/Content/Images/placeholder.gif", "Genre": { "Id": "genres/1", "Name": "Rock" }, "Price": 8.99, "Title": "Californication", "CountSold": 0, "Artist": { "Id": "artists/127", "Name": "Red Hot Chili Peppers" } } RavenDB Document
9. SQL Database Differences NoSQL Database • Contains tables • A row in a table is a record • A record can have primary and secondary keys to related data • Data can be queried using SQL • Complex Queries can be built using functions, stored procedures and views • Int32, Int64, DateTime, Varchar, byte… • ADO.NET • Contains documents • A document is like a row in a table • Stores an entire graph of your object – an entity • Data can be queried using Linq • Complex queries can be built by building indexes and using MapReduce • String, int, DateTime • JSON or XML
10. SQL Database Users Differences NoSQL Users
11. SQL Database MapReduce NoSQL Database • Views • Functions • Stored Procedures • Get the data you need (map) • Manipulate the data to get what you need (reduce)
12. SQL What’s out there? NoSQL
13. Using NoSQL • Facebook • Twitter • LinkedIn • Google • Amazon • eBay • Digg •aurion?
14. Any Questions?
15. Thanks 