Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Transcript of NoSQL Controversy
30 years of standstill
Big database vendors and DBAs ruled
People forgot how to build databases (cf. prohibition in the USA, http://blog.8thlight.com/uncle-bob/2012/05/15/NODB.html)
History repeates itself:
"[Teradata]'s very similar to the Tandem story: it's a sort of one-trick pony. It doesn't have referential integrity; it doesn't have all the fanciness. You give it SQL; it gives you back the answers, very fast, and presumably cheaply, because it's running on Intel processors and on commodity disks." http://www.mcjones.org/System_R/SQL_Reunion_95
Ted Neward (2004): "Object-Relational mapping is the Vietnam of our industry"
Schema changes get easier
At least at first
Schemaless development is great
Schemaless ops are a nightmare
Polyglott persistence is great
If you can handle it
"Nobody gets fired for choosing IBM"
RDBMS: What answers do I have?
NoSQL: What questions do I have?
You don't always need multi-document transactions,
Different structure (embedded documents, arrays)
Add entity or do cleanup -> try-catch on unique attribute
Application- vs data-view,
who is the gatekeeper?
"KnowSQL is the new NoSQL"