NoSQL
Get flash to fully experience Pearltrees
www.BenStopford.com » Blog Archive » Shared Nothing v.s. Shared Disk Architectures: An Independent View
The Shared Nothing Architecture is a relatively old pattern that has had a resurgence of late in data storage technologies, particularly in the NoSQL, Data Warehousing and Big Data spaces. As architectures go it’s fairly polar, providing the potential for huge gains for certain use cases but also the potential for huge losses in others. This article focuses on its application in disk based persistent stores. More specifically it contrasts Shared Nothing with Shared Disk Architectures. Shared Disk and Shared Nothing?
Brian Ritchie has two posts ( ☞ here and ☞ here ) covering three document databases: CouchDB, MongoDB, and RavenDB concluding with the matrix below: But before using this as a reference material there are a couple of corrections needed: They have some special characteristics that make them kick some serious SQL.
Document Databases Compared: CouchDB, MongoDB, RavenDB
Consider the following two scenarios: Scenario no. 1 – traditional database design method The DBA will use the following SQL statements in order to create two additional columns: In our example, we will update the data that already exists in the table with the following update sql statements: This will make our table look like this:
Traditional database design vs. key-value table - MySQL
NoSQL Relational Database Management System: Home Page
A Relational Database Management System NoSQL is a fast, portable, relational database management system without arbitrary limits, (other than memory and processor speed) that runs under, and interacts with, the UNIX 1 Operating System. It uses the "Operator-Stream Paradigm" described in "Unix Review", March, 1991, page 24, entitled "A 4GL Language".
