IN THE <br />NAME OF<br />GOD<br />
NoSQL<br />Abolfazlghalenoi<br />Mostafaalinaghipour<br />
What’s the meaning?<br /><ul><li> Any database that is not relational
 Not Only Sql
 It’s not about  don’t use sql
 Stored data may not require fixed table schemas</li></ul>User_tbl->{  name:’ali’ , phone->{home:’+125235456’ , office:’+1...
Contents complexity
Architectures weakness</li></li></ul><li>Why NoSQL?<br />DATA SIZE<br />Size of data stored per year [2006-2010]<br />
Why NoSQL?<br />Contents complexity<br />GGGs<br />WEB 1.0<br />WEB 2.0<br />WEB 3.0<br />Ontology (information science)<b...
Why NoSQL?<br />Architectures weakness<br />Application<br />Application<br />Application<br />Application<br />Applicatio...
How about Perfomance?<br />                          RDBMS Performance <br />Applictions<br />Salary List<br />Relational ...
Content structure in NoSQL<br /><ul><li>Key-Value stores structure
Document  database  structure
Graph databases</li></li></ul><li>Content structure in NoSQL<br />Key-Value stores structure<br />Name_231@ali@alavi@...<b...
Content structure in NoSQL<br />Document  database  structure<br />{<br />  name:  ”ali”,<br />familt:   “alavi”,<br />   ...
Upcoming SlideShare
Loading in...5
×

Nosql

1,126

Published on

Published in: Health & Medicine
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,126
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
22
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Nosql

  1. 1. IN THE <br />NAME OF<br />GOD<br />
  2. 2. NoSQL<br />Abolfazlghalenoi<br />Mostafaalinaghipour<br />
  3. 3. What’s the meaning?<br /><ul><li> Any database that is not relational
  4. 4. Not Only Sql
  5. 5. It’s not about don’t use sql
  6. 6. Stored data may not require fixed table schemas</li></ul>User_tbl->{ name:’ali’ , phone->{home:’+125235456’ , office:’+122344554’ } }<br />User_tbl->{ name:’reza’, family=‘rezai’}<br />Why NoSQL?<br /><ul><li>Data size
  7. 7. Contents complexity
  8. 8. Architectures weakness</li></li></ul><li>Why NoSQL?<br />DATA SIZE<br />Size of data stored per year [2006-2010]<br />
  9. 9. Why NoSQL?<br />Contents complexity<br />GGGs<br />WEB 1.0<br />WEB 2.0<br />WEB 3.0<br />Ontology (information science)<br />Search engines<br />Folksonomies<br />Social networks<br />complexity<br />Tagging<br />Wikis<br />Micro blogs<br />Blogs<br />Feeds<br />Hypertext<br />Text Documents<br />1988<br />2000<br />1990<br />2010<br />2006<br />2020<br />
  10. 10. Why NoSQL?<br />Architectures weakness<br />Application<br />Application<br />Application<br />Application<br />Application<br />DB<br />DB<br />DB<br />DB<br />Application<br />Application<br />Application<br />Primitive Architecture<br />Current Architecture<br />NoSQL Architecture<br />
  11. 11. How about Perfomance?<br /> RDBMS Performance <br />Applictions<br />Salary List<br />Relational database<br />Majority of web sites<br />Performance<br />Social networks<br />Semantic Web<br />Content complexity<br />
  12. 12. Content structure in NoSQL<br /><ul><li>Key-Value stores structure
  13. 13. Document database structure
  14. 14. Graph databases</li></li></ul><li>Content structure in NoSQL<br />Key-Value stores structure<br />Name_231@ali@alavi@...<br />user29<br />key<br /> value<br /> Note: The value has no meaning for DBMS<br />
  15. 15. Content structure in NoSQL<br />Document database structure<br />{<br /> name: ”ali”,<br />familt: “alavi”,<br /> address: ”mashh..”<br />}<br />user29<br />key<br />document<br /> Note: The value understood by DBMS<br />
  16. 16. Content structure in NoSQL<br />Graph databases<br />ali<br />name<br />alavi<br />family<br />author<br />blog12<br />user23<br />alavi@yahoo.com<br />admin<br />email<br />author<br />user2<br />family<br />blog22<br />name<br />phone<br />rezai<br />reza<br />+123325645<br />
  17. 17. Content structure in NoSQL<br />Key-Value Db<br />Performance<br />Document DB<br />Graph DB<br />Complexity<br />
  18. 18. Save formats<br /> YAML<br />---<br />Name: ali<br />Family: alavi<br />Email:<br />yahoo:ali.alavi@yahoo.com<br />gmail:ali.alavi@gmail.com<br />--<br /> XML<br /><user><br /> <name>ali</name><br /><family>alavi</family><br /><email provider=“yahoo” >ali.alavi@yahoo.com</email><br /> <email provider=“gmail” >ali.alavi@gmail.com</email><br /></user><br /> JSON<br />{<br /> "firstName": “ali" ,<br /> "lastName": “alavi", <br /> “email”: <br /> {<br /> {<br /> “provider”:”yahoo:,<br /> “address”:” ali.alavi@yahoo.com”<br /> }<br /> {<br /> “provider”:”gmail:,<br /> “address”:” ali.alavi@gmail.com”<br /> }<br /> } <br />}<br />
  19. 19. NoSQl Futures<br /><ul><li> Massive scalability
  20. 20. High availability
  21. 21. More flexible schema
  22. 22. Better performance in complex contents</li></ul>NoSQl Disadvantage<br /><ul><li> Limited query capability
  23. 23. Low security
  24. 24. No standardization
  25. 25. Portability might be an issue
  26. 26. Application program is more complicated</li></li></ul><li>Enng.manp@gmail.com<br />
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×