1. IN THE NAME OF GOD

2. NoSQL Abolfazlghalenoi Mostafaalinaghipour

4. Not Only Sql

5. It’s not about don’t use sql

7. Contents complexity

9. Why NoSQL? Contents complexity GGGs WEB 1.0 WEB 2.0 WEB 3.0 Ontology (information science) Search engines Folksonomies Social networks complexity Tagging Wikis Micro blogs Blogs Feeds Hypertext Text Documents 1988 2000 1990 2010 2006 2020

10. Why NoSQL? Architectures weakness Application Application Application Application Application DB DB DB DB Application Application Application Primitive Architecture Current Architecture NoSQL Architecture

11. How about Perfomance? RDBMS Performance Applictions Salary List Relational database Majority of web sites Performance Social networks Semantic Web Content complexity

13. Document database structure

15. Content structure in NoSQL Document database structure { name: ”ali”, familt: “alavi”, address: ”mashh..” } user29 key document Note: The value understood by DBMS

16. Content structure in NoSQL Graph databases ali name alavi family author blog12 user23 alavi@yahoo.com admin email author user2 family blog22 name phone rezai reza +123325645

17. Content structure in NoSQL Key-Value Db Performance Document DB Graph DB Complexity

18. Save formats YAML --- Name: ali Family: alavi Email: yahoo:ali.alavi@yahoo.com gmail:ali.alavi@gmail.com -- XML <user> <name>ali</name> <family>alavi</family> <email provider=“yahoo” >ali.alavi@yahoo.com</email> <email provider=“gmail” >ali.alavi@gmail.com</email> </user> JSON { "firstName": “ali" , "lastName": “alavi", “email”: { { “provider”:”yahoo:, “address”:” ali.alavi@yahoo.com” } { “provider”:”gmail:, “address”:” ali.alavi@gmail.com” } } }

20. High availability

21. More flexible schema

23. Low security

24. No standardization

25. Portability might be an issue