StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POWhich of CouchDB or MongoDB suits my needs?
text
Body
copied!<p>Where I work, we use Ruby on Rails to create both backend and frontend applications. Usually, these applications interact with the same MySQL database. It works great for a majority of our data, but we have one situation which I would like to move to a NoSQL environment.</p> <p>We have clients, and our clients have what we call "inventories"--one or more of them. An inventory can have many thousands of items. This is currently done through two relational database tables, <code>inventories</code> and <code>inventory_items</code>.</p> <p>The problems start when two different inventories have different parameters:</p> <pre><code># Inventory item from inventory 1, televisions { inventory_id: 1 sku: 12345 name: Samsung LCD 40 inches model: 582903-4 brand: Samsung screen_size: 40 type: LCD price: 999.95 } # Inventory item from inventory 2, accomodation { inventory_id: 2 sku: 48cab23fa name: New York Hilton accomodation_type: hotel star_rating: 5 price_per_night: 395 } </code></pre> <p>Since we obviously can't use <code>brand</code> or <code>star_rating</code> as the column name in <code>inventory_items</code>, our solution so far has been to use generic column names such as <code>text_a</code>, <code>text_b</code>, <code>float_a</code>, <code>int_a</code>, etc, and introduce a third table, <code>inventory_schemas</code>. The tables now look like this:</p> <pre><code># Inventory schema for inventory 1, televisions { inventory_id: 1 int_a: sku text_a: name text_b: model text_c: brand int_b: screen_size text_d: type float_a: price } # Inventory item from inventory 1, televisions { inventory_id: 1 int_a: 12345 text_a: Samsung LCD 40 inches text_b: 582903-4 text_c: Samsung int_a: 40 text_d: LCD float_a: 999.95 } </code></pre> <p>This has worked well... up to a point. It's clunky, it's unintuitive and it lacks scalability. We have to devote resources to set up inventory schemas. Using separate tables is not an option.</p> <p>Enter NoSQL. With it, we could let each and every item have their own parameters and still store them together. From the research I've done, it certainly seems like a great alterative for this situation.</p> <p>Specifically, I've looked at CouchDB and MongoDB. Both look great. However, there are a few other bits and pieces we need to be able to do with our inventory:</p> <ul> <li>We need to be able to select items from only one (or several) inventories.</li> <li>We need to be able to filter items based on its parameters (eg. get all items from inventory 2 where type is 'hotel').</li> <li>We need to be able to group items based on parameters (eg. get the lowest price from items in inventory 1 where brand is 'Samsung').</li> <li>We need to (potentially) be able to retrieve thousands of items at a time.</li> <li>We need to be able to access the data from multiple applications; both backend (to process data) and frontend (to display data).</li> <li>Rapid bulk insertion is desired, though not required.</li> </ul> <p>Based on the structure, and the requirements, are either CouchDB or MongoDB suitable for us? If so, which one will be the best fit?</p> <p>Thanks for reading, and thanks in advance for answers.</p> <p>EDIT: One of the reasons I like CouchDB is that it would be possible for us in the frontend application to request data via JavaScript directly from the server after page load, and display the results without having to use any backend code whatsoever. This would lead to better page load and less server strain, as the fetching/processing of the data would be done client-side.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload