SQL/NoSQL How to choose ?
•
106 j'aime•50,601 vues
The document discusses choosing between SQL and NoSQL databases. It covers the evolution of data architectures from traditional client-server models to newer distributed NoSQL solutions. It provides an overview of different data store types like SQL, NoSQL, key-value, document, column family, and graph databases. The document advises picking the right data model based on business needs, use cases, data storage requirements, and growth patterns then evaluating solutions based on pros and cons. It concludes that for large, growing data, both SQL and NoSQL solutions may be needed.
![Who am I ,[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommandé
Contenu connexe
Tendances
Tendances (20)
Similaire à SQL/NoSQL How to choose ?
Similaire à SQL/NoSQL How to choose ? (20)
Dernier
Dernier (20)
SQL/NoSQL How to choose ?
- 1. SQL or NoSQL How to choose Venu Anuganti Jan 2011 http://venublog.com/
Notes de l'éditeur
- MySQL Employee 2000-2004 Database Companies MySQL SOLID ANTs Data Server ScaleDB Part of Yahoo’s cloud initiates like Sherpa and Mobstor and a platform MySQL Geek Still contribute randomly to MySQL source
- To answer all these, we need to understand how the traditional data architecture is and how it is currently used and the future of data
- When web is read-only, things used to scale with one or more systems with caching or LB in the front But as things change to real-time and interactive, the same architecture can’t keep up Talk about how Facebook, Twitter, LinkedIn is evolving Public cloud sucks in performance, but offers elasticity to grow ; but you need to design systems to balance hardware, performance and scalability
- If Facebook, Twitter or someone else uses NoSQL, does not mean everyone has to use it If someone scales using MySQL, does not mean everyone can use the same concept
- Caching was used for scaling reads
- Caching was used for scaling reads
- Caching was used for scaling reads
- When web is read-only, things used to scale with one or more systems with caching or LB in the front But as things change to real-time and interactive, the same architecture can’t keep up Talk about how Facebook, Twitter, LinkedIn is evolving Public cloud sucks in performance, but offers elasticity to grow ; but you need to design systems to balance hardware, performance and scalability
- Not everyone wants to hear about systems going down for hours and hours or even days Like FourSquare, Tumbler
- Typical OLTP system needs C & A Replication is also eventual consistency Eventually consistent
- Now lets understand different types of data stores
- Widely adopted for years
- Widely adopted for years
- Widely adopted for years
- Widely adopted for years
- DCA Data Computing Appliance Talk about analytics and how crucial they are now
- Bunch of cloud based solutions, which are bit surprising
- Bunch of cloud based solutions, which are bit surprising
- Bunch of cloud based solutions, which are bit surprising
- Before getting into how to design and implement, lets understand some basics of design, what to achieve
- Twitter – MySQL crash and no proper backups in place.. Rolling restore Tumblr … it was down for close to 16 hours or so FourSuare is down for 12 hrs or so You don’t want to be a in situation where you don’t know where the problem is
- Employee or user can update his profile fields Guaranteed durability
- Employee or user can update his profile fields Guaranteed durability
- Employee or user can update his profile fields Guaranteed durability
- Gaming is a classic example for volatile data
- Gaming is a classic example for volatile data
- Gaming is a classic example for volatile data
- Gaming is a classic example for volatile data
- Gaming is a classic example for volatile data
- Gaming is a classic example for volatile data
- Gaming is a classic example for volatile data
- Gaming is a classic example for volatile data