Three Developer Abilities They Dont Teach In College
SQL vs NoSQL
1. SQL vs. NoSQL
Data in the world of social media
Jon Limjap
Microsoft MVP for C#
2. Who am I?
• I’m Jon
– Blog: http://dotnet.kapenilattex.com
– Twitter: @lattex
• Does anybody remember…
• I’m a developer, not a DBA
• I’ve worked on mainframe, desktop, web, and
mobile
• I’m a member of MSDEV.PH / PHISSUG /
DevCon
4. Why not SQL?
• Internet scale
• 100s of millions of concurrent users
• Massive data collections – Terabytes to
Petabytes of data
• 24/7 across the globe
15. ACID vs. BASE
• ACID:
– Atomic: Every transaction should succeed else
transaction is roled back
– Consistent: Every transaction leaves database in a
valid (consistent) state
– Isolation: Transactions don’t interfere with each
other
– Durable: Completed transactions persist, even
when servers restart
16. ACID vs. BASE
• BASE
– Basic Availability: The data store should be up all
of the time
– Soft state: The data store can be cached
somewhere else if the data store is not available
– Eventual consistency: The data store can have
conflicting transactions, but should eventually
reach a valid state
20. References
• John D. Cook – ACID versus BASE for database transactions
http://www.johndcook.com/blog/2009/07/06/brewer-cap-
theorem-base/
• Getting Started with MongoDB Development –
http://docs.mongodb.org/manual/tutorial/getting-started/
• Michael Rys – SQL and NoSQL Are Two Sides of the Same
Coin – http://www.slideshare.net/MichaelRys/sql-and-
nosql-are-two-sides-of-the-same-coin-strata-2012
• Vamshi Krishna Reddy Vangapally – No sql databases -
http://www.slideshare.net/vamshi4001/no-sql-databases
• Venu Anuganti – SQL, NoSQL, BigData in Data Architecture -
http://www.slideshare.net/vanuganti/sql-nosql-bigdata-in-
data-architecture