Databases
StackOverflow2013
Postsdbo
POSQL vs NoSQL for data that will be presented to a user after multiple filters have been added
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSQL vs NoSQL for data that will be presented to a user after multiple filters have been added
    primarykey
    data
    text
    <p>I am about to embark on a project for work that is very outside my normal scope of duties. As a SQL DBA, my initial inclination was to approach the project using a SQL database but the more I learn about NoSQL, the more I believe that it might be the better option. I was hoping that I could use this question to describe the project at a high level to get some feedback on the pros and cons of using each option.</p> <p>The project is relatively straightforward. I have a set of objects that have various attributes. Some of these attributes are common to all objects whereas some are common only to a subset of the objects. What I am tasked with building is a service where the user chooses a series of filters that are based on the attributes of an object and then is returned a list of objects that matches all^ of the filters. When the user selects a filter, he or she may be filtering on a common or subset attribute but that is abstracted on the front end. </p> <p><em>^ There is a chance, depending on user feedback, that the list of objects may match only some of the filters and the quality of the match will be displayed to the user through a score that indicates how many of the criteria were matched.</em></p> <p>After watching this talk by Martin Folwler (<a href="http://www.youtube.com/watch?v=qI_g07C_Q5I" rel="noreferrer">http://www.youtube.com/watch?v=qI_g07C_Q5I</a>), it would seem that a document-style NoSQL database should suit my needs but given that I have no experience with this approach, it is also possible that I am missing something obvious. </p> <p>Some additional information - The database will initially have about 5,000 objects with each object containing 10 to 50 attributes but the number of objects will definitely grow over time and the number of attributes could grow depending on user feedback. In addition, I am hoping to have the ability to make rapid changes to the product as I get user feedback so flexibility is very important. </p> <p>Any feedback would be very much appreciated and I would be happy to provide more information if I have left anything critical out of my discussion. Thanks. </p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USzgall1
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSQL vs NoSQL for data that will be presented to a user after multiple filters have been added
      1. USzgall1
      1. VTBountyStart
    2. VO
      singulars
      1. POSQL vs NoSQL for data that will be presented to a user after multiple filters have been added
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POSQL vs NoSQL for data that will be presented to a user after multiple filters have been added
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO5000 objects seems excessive in any schema...is that 5000 tables? Are you planning a table per customer or something? Unless you are able to find/hire a dedicated NoSQL resource for you, learning as you go seems painful here...I'd recommend sticking to what you are comfortable and familiar with for an implementation of this scale.
      singulars
      1. POSQL vs NoSQL for data that will be presented to a user after multiple filters have been added
      1. USTwelfth
    2. COMaybe I misused terminology here. By 5000 objects, I meant what would be considered 5000 rows in a SQL database.
      singulars
      1. POSQL vs NoSQL for data that will be presented to a user after multiple filters have been added
      1. USzgall1
    3. CO@Twelfth Does my clarification make sense?
      singulars
      1. POSQL vs NoSQL for data that will be presented to a user after multiple filters have been added
      1. USzgall1
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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