patterns & practices: Data Access Guidance code drop for the "Data Access for Highly-Scalable Solutions: Using SQL, NoSQL, and Polyglot Persistence" eBook now available
Patterns and Practices Data Access Guide.Source.Exe
application, 1412K, uploaded Today - 5 downloads
Other Available Downloads
application, 895K, uploaded Today - 8 downloads
application, 427K, uploaded Today - 7 downloads
documentation, 8903K, uploaded Today - 8 downloads
application, 4020K, uploaded Today - 3 downloads
This is the 2013 release of Data Access Guidance.
The documentation for this RI is also available on MSDN:
Data Access for Highly-Scalable Solutions: Using SQL, NoSQL, and Polyglot Persistence:
Data Access Guidance project covers data access for SQL and NoSQL databases as well as some architectural and design decisions involved in using them.
OverviewThis project is guidance around data access using relational databases, as well as NoSQL databases. It describes the various types of data persistence technologies, as well as when, how, and why they should be used. The guidance will show how various persistence types can be used together to create a highly-scalable system, as well as illustrating the challenges that arise when moving to a polyglot persistent system.
Here's a snip from the readme.pdf;
This document describes how to configure the Visual Studio example solution that accompanies the guide Building Highly-Scalable Solutions for Storing and Retrieving Data Using SQL and NoSQL Databases. This guide focuses on the common issues that you may encounter when building applications that need to store data in a variety of different data stores, such as a relational database, a key-value store, a document database, or a graph database.
This document contains the following sections:
About the Example Solution describes the high level structure of the sample application.
Before You Start describes the procedures that you must follow before configuring and running the application.
Supported Scenarios describes how to build and run the application in each of the scenarios described in the guide.
Configure the Application describes how to modify the configuration to support each of the scenarios described in the guide.
Check the Sample Functionality describes how to verify that the application is running correctly.
About the Example Solution
The example solution implements a shopping application that enables customers to browse products and place orders. The application runs by using the web. Orders are handled by a separate order service, and for completeness the example solution includes a simulation of this order service.
The Shopping application is a polyglot system that stores the data it uses in a variety of different repositories. Each repository was selected to meet the business requirements of a specific scenario in the application:
Customer information is stored in a relational database.
Shopping cart information is stored in a key/value store.
Product information is stored in a document database.
Active order information is stored in a relational database.
Order history information is stored in a document database.
Product recommendations are stored in a graph database.
Not a simple project, which given all the data sources, kinds of makes sense... I mean a 22 page readme just to get the code working...