Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I can only answer your question partially but hopefully more than a comment.</p> <p>MongoDB is not typically a key-value store and has been known to have certain performance hits when used as one.</p> <p>MongoDb also has a locking problem here that could come back to haunt you. It has a DB level lock atm which means it could (would need testing) cause write lock saturation.</p> <p>It is also heavily designed for a 80% read app (which is said to be the most common setup for websites now-a-days) so the more writes you do the more you will notice a performance drop over time. That being said you can tweak MongoDB to be more write friendly and the distributed nature does help to stop write lock saturation a little.</p> <p>However that being said my personal opinion the learning curve of MongoDB from SQL:</p> <ul> <li>Was next to <code>null</code></li> <li>More natural and simpler to implement into my app than SQL</li> <li>Query language is simple making it dead easy to get to grips with</li> <li>Query language has a lot of similarities to SQL</li> <li>The drivers are standardised so that the syntax you see in the Docs for the JS driver in the console is consistent across the board.</li> </ul> <p>My personal opinion on the general matter is the distributed notion of it. If you get a NoSQL solution designed for key-value stores then it could be really good. A quick search on Google pulled out a small list of NoSQL key-value stores on Wikipedia: <a href="http://en.wikipedia.org/wiki/NoSQL#Key-value_stores_on_solid_state_or_rotating_disk" rel="nofollow">http://en.wikipedia.org/wiki/NoSQL#Key-value_stores_on_solid_state_or_rotating_disk</a> </p>
    singulars
    1. This table or related slice is empty.
    1. POIs there a high performance difference in a Key-Value db on a single server with MySQL vs. NoSQL
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USSammaye
    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. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COmongodb 2.2 instead of global write lock has [per collection lock](https://jira.mongodb.org/browse/SERVER-4328).
      singulars
      1. PO
      1. USAndrew Orsich
    2. CO@AndrewOrsich Nah it has DB level lock. Collection level lock is coming much later, here is the JIRA for it: https://jira.mongodb.org/browse/SERVER-1240
      singulars
      1. PO
      1. USSammaye
    3. COexcuse me, they have [db level lock](http://docs.mongodb.org/manual/reference/server-status/#locks) now
      singulars
      1. PO
      1. USAndrew Orsich
 

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