This will be an interesting and sometimes fun session with a small demo. This session will answer some of your questions and force you to think about new questions. It will not be very technical, so it's ok for choose another more technical session from the schedule :) But if will decide to come, I can assure you, that you will not be disappointed. We will do a thought experiment with one famous public high-loaded website, will look at advantages and disadvantages of SQL and NoSQL databases, and will choose the best database engine for it.
Top profile Call Girls In Tumkur [ 7014168258 ] Call Me For Genuine Models We...
SQL vs. NoSQL. It's always a hard choice.
1. SQL vs NoSQL
It’s Always a Hard Choice
Denis Reznik
Data Architect at Intapp, Inc.
Microsoft Data Platform MVP
2. About me
• Denis Reznik
• Kyiv, Ukraine
• Data Architect at Intapp, Inc.
• Microsoft Data Platform MVP
• Co-Founder Ukrainian Data Community
• PASS Regional Mentor, Central, and Eastern Europe
• Author of “SQL Server MVP Deep Dives 2” Chapter 19
2 |
3. Database History
1960s 1970s 1980s 1990s 2000s Nowadays
Object
Databases
RDMS
Commercial
Success
SQL
RDBMS
Ingress
System R
E.F. Codd’s
Paper
CODASYL
IMS
NoSQL
(Johan Oskarsson)
NewSQL (?)
Google BigTable
Paper
Amazon Dynamo
Paper
13. Sample Workload
• 4 million users
• 8 million questions
• 40 million answers
• As a network #54 site for traffic in the world
• 560 million page views a month
• Peak is more like 2600-3000 requests/sec on most
weekdays.
source: https://www.youtube.com/watch?v=t6kM2EM6so4
15. Scalability
• Scale up
• Very easy to scale
• Always have a limit
• Hardware is expensive
• Scale-out
• Relatively tricky scaling
• Theoretically infinite scale
• Can be done on commodity hardware
19. Cost
• Hardware
• Big servers are expensive
• Small servers are cheep
• Small servers can be easily replaced
• License
• A lot of NoSQL databases are free
• There are free RDBMS as well
• Scale Out is more useful for free software
• Support
• MSSQL forgives you more than MySQL
25. More Points
• “Respect the problem” (c)
• Think about the future workload grows
• Think about the future application changes
• Database itself, even if it is blazing fast, is not a purpose of
not to use cache
• Consider cloud database offers
• Consider Polyglot Persistence
• Consider using service tier for data access in application
• Easier database exchange
• Tire scaling
• A/B testing