3. What?
It is a Fully managed, highly scalable,
queryable, truly schema-free JSON document
database, delivered as a service for modern
applications.
4. Why?• Produce and consume data at a staggering
rate while requiring near instantaneous
response times to match user experiences.
• Developed iteratively with many versions
supported concurrently and continuously
evolving data models.
• Increasingly complex, compensating for the
lack of query and transactional processing
in today’s NoSQL database systems.
• Experience unpredictable and explosive
growth.
Editor's Notes
What
When they did document db they had 3 main goals they really wanted to nail.
Fully managed and delivered as a service
Scalable, you keep adding capacity and they keep giving you more stuff to use
The promise to deliver on schema free – not just allowing you to store data in any structure you like but also be able to query on the different schemas without having to do anything first.
SQL = Schema enforced by a RDBMS on Write
NoSQL = Partial Schema enforced by the DBMS on Write, PLUS schema fully enforced by the Application on Read (Externalised schema)
So while a supposed Schema-less NoSQL data-store will in theory allow you to store any data you like (typically key value pairs, in a document) without prior knowledge of the keys, or data types, it will be pointless unless you have some mechanism to retrieve and use the data. So essentially the schema is partially moved from the RDBMS into the application code.
A relational database management system (RDBMS) is a database management system (DBMS) that is based on the relational model
Why
Why the need for no sql, why the need for documentDB
The applications we build today produce and consume data like never before.
Microsoft Azure DocumentDB is a highly-scalable NoSQL document database-as-a-service that offers rich querying over schema-free data, helps deliver configurable and reliable performance, and enables rapid development, all through a managed platform backed by the power and reach of Microsoft Azure. DocumentDB is the right solution for web and mobile applications when predictable throughput, low latency, and a schema-free data model are key requirements. DocumentDB delivers schema flexibility and rich indexing via a native JSON data model, and includes multi-document transactional support with integrated JavaScript.
What kind of database is DocumentDB?
DocumentDB is a NoSQL document oriented database that stores data in JSON format. DocumentDB supports nested, self-contained-data structures that can be queried through a rich DocumentDB SQL query grammar. DocumentDB provides high performance transactional processing of server side JavaScript through stored procedures, triggers, and user defined functions. The database also supports developer tunable consistency levels with associated performance levels.
Database-as-a-Service (DBaaS) is a service that is managed by a cloud operator (public or private) that supports applications, without the application team assuming responsibility for traditional database administration functions.
Sign in to the online Microsoft Azure Preview portal.
In the Jumpbar, click New, then click Data + Storage, and then click Azure DocumentDB.
In the New DocumentDB account blade, specify the desired configuration for the DocumentDB account.
Or, you can monitor your progress from the Notifications hub.
After the DocumentDB account is created, it is ready for use with the default settings in the online portal. Note that the default consistency of the DocumentDB account is set to Session. You can adjust the default consistency setting by clicking the Default Consistency tile on the DocumentDB account blade.
The values for EndpointUrl and AuthorizationKey are the URI and PRIMARY KEY for your DocumentDB account, which can be obtained from the Keys blade for your DocumentDB account.
Step 1: Create a DocumentDB account
Step 2: Setup your Visual Studio Solution
Step 3: Connect to a DocumentDB account
Step 4: Create a database
Step 5: Create a collection
Step 6: Create documents
Step 7: Query DocumentDB resources
Step 8: Delete the database
Step 9: Run your application!