<h1>Project Description</h1>
<p>
Our project will involve a comparative study of different document store database systems. The 5 systems we will be examining will be MongoDB, OrientDB, Couchbase, Redis and Apache Cassandra.

We will use the Yahoo! Cloud Serving Benchmark (YCSB) framework to collect data on the performance of each system. Performance will be tested by running common workloads across all of the systems using the YCSB client which is an open source workload generator. In addition to a predefined set of "Core" workloads already provided by YCSB, due to the extensible nature of the client, we will be able to define new workloads and look at performance from different aspects and test various scenarios

By the end of this study, we hope to achieve a better understanding of how document store databases perform in a distributed environment and how different offerings of document stores perform relative to each other under similar conditions. We also expect to gain a deeper appreciation of the challenges behind distributed systems in the context of databases.
</p>
<h1>Goals</h1>
<ul><li>Gather and compare performance analytics of several distributed databases under YCSB workloads as well as custom workloads</li>
<li>Implement unsupported database interfaces into the YCSB framework</li>
<li>Learn about distributed document-stores</li>
<li>Extend YCSB with custom workloads</li>

<li>Run workloads under simulated failure of nodes and analyze results</li>
<ul><li>1/5 node “unplugged”</li>
<li>2/5 nodes
</ul>

<h1>Final Deliverables</h1>
<ul><li>A comprehensive report comparing 5 select document store databases outlining key differences in performance and scalability under varying workflows and within a distributed environment</li>
<li>If time permits, interface adapters and workflow extensions written throughout the lifecycle of the project may be added as contributions to the YCSB framework</li>
</ul>

<h1>Internal Milestones</h1>
<ol>
<li>Get a YCSB instance up and running with the core workload ( Feb 11 )
</li>
<li>Add client interfaces if ones do not exist ( Feb 18th )
</li>
<li>Run core workloads on our databases and analyze results (local) ( Feb 22nd )
</li>
<li>Configure Amazon instances to use same resources (RAM, HDD/SSD speed, processors, caches); Snapshots, system images, schemes ( Mar 3rd )
</li>
<li>Set up databases on instances ( Mar 8th )
</li>
<li>Collect data ( Mar 15th )
</li>
<li>Data analysis and 1st Report Draft Done ( Mar 29th )
</li>
</ol>

<h1>Division Of Work</h1>

<ul>
<li>Each group member will be assigned to 1 out of the 5 databases and
</li>
<ul>
<li>research its implementation, constraints, benefits
</li>
<li>write a client adaptor if necessary inside of the YCSB framework
</li>
<li>run YCSB workloads against the database
</li>
<li>be responsible for the results and comparing them against the other 4 databases
</li>
</ul>
</ul>


<h1>Wish List ( If Time Permits)</h1>
<ul>
<li>Perform further benchmarks on other well-known document store databases already supported by YCSB</li>
<li>Expand on various test scenarios and extend YCSB benchmarking workloads with custom tests
</li>
<li>Contribute extensions to the existing YCSB framework
</li>
</ul>

<h1>Risk Management</h1>

<p>Due to the modular nature of our goals we can choose not to do extended workflows or write our own workflows if the core workflow is proving too complex to analyze effectively under time constraints.
</p>

<h1>Tools, Scripts, Acknowledgements</h1>

<p>We will be relying heavily on research papers, documentation, and the YCSB benchmark framework for our report.</p>

<h1>Project References</h1>
<table border="1">
<tr>
<th>Links To Reference Documents</th>
</tr>
<tr>
<td><a
</tr>
<tr>
<td><a Research
</tr>
<tr>
<td><a Experimental
</tr>
<tr>
<td><a GitHub Source
</tr>
<tr>
<td><a
">YCSB - new
</tr>
<tr>
<td><a
">Core
</tr>
<tr>
<td><a
">List of wiki pages for
</tr>
<tr>
<td><a

</tr>
<tr>
<td><a

</tr>
<tr>
<td><a

</tr>
<tr>
<td><a

</tr>
<tr>
<td><a

</tr>
</table>


<h1>Project Progress</h1>

<a Description and Progress</a>