@@ -1164,3 +1164,45 @@ Graphs databases offer high performance for data models with complex relationshi
11641164* [ Scalability] ( http://www.lecloud.net/post/7994751381/scalability-for-dummies-part-2-database )
11651165* [ Introduction to NoSQL] ( https://www.youtube.com/watch?v=qI_g07C_Q5I )
11661166* [ NoSQL patterns] ( http://horicky.blogspot.com/2009/11/nosql-patterns.html )
1167+
1168+ ### SQL or NoSQL
1169+
1170+ <p align =" center " >
1171+ <img src =" http://i.imgur.com/wXGqG5f.png " >
1172+ <br />
1173+ <i ><a href=https://www.infoq.com/articles/Transition-RDBMS-NoSQL/>Source : Transitioning from RDBMS to NoSQL</a ></i >
1174+ </p >
1175+
1176+ Reasons for ** SQL** :
1177+
1178+ * Structured data
1179+ * Strict schema
1180+ * Relational data
1181+ * Need for complex joins
1182+ * Transactions
1183+ * Clear patterns for scaling
1184+ * More established: developers, community, code, tools, etc
1185+ * Lookups by index are very fast
1186+
1187+ Reasons for ** NoSQL** :
1188+
1189+ * Semi-structured data
1190+ * Dynamic or flexible schema
1191+ * Non relational data
1192+ * No need for complex joins
1193+ * Store many TB (or PB) of data
1194+ * Very data intensive workload
1195+ * Very high throughput for IOPS
1196+
1197+ Sample data well-suited for NoSQL:
1198+
1199+ * Rapid ingest of clickstream and log data
1200+ * Leaderboard or scoring data
1201+ * Temporary data, such as a shopping cart
1202+ * Frequently accessed ('hot') tables
1203+ * Metadata/lookup tables
1204+
1205+ ##### Source(s) and further reading: SQL or NoSQL
1206+
1207+ * [ Scaling up to your first 10 million users] ( https://www.youtube.com/watch?v=vg5onp8TU6Q )
1208+ * [ SQL vs NoSQL differences] ( https://www.sitepoint.com/sql-vs-nosql-differences/ )
0 commit comments