As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I am a Mongo newbie and wanted to know if there are any tools that will help me test MongoDB? Especially, if they help me automate testing of the tables (or collections) in MongoDB. I did a few internet searches but got very confused. Any help will be appreciated.
Thanks!
Two clients I found useful when testing/looking at data within the db are:
MongoVue - It's free and allows you to see up to 3 documents at a time; and has multiple ways of displaying the data (text form, table form, etc.) Quite nifty, but the cool features expire after 14 days, then you have to pay.
MongoExplorer - It's a little less friendly looking thatn MongoVue, but it is very simple to use, and it is absolutely free. It has some more advanced options as well - such as the ability to see GridFS data (this is a paid feature in MongoVue).
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I am trying to evaluate whether to use mongoDB or MySQL memory engine for storing and retrieving emails. Basically I have an application where it has to decide whether to send email to the user or not based on the email presence in this table. It may contain over 12 million entries. Please suggest.
Email store well suited to mongodb. Many people already doing this. Sammaye correct on 12 million documents being walk in park.
General guidance on use cases
here
Bear in mind that there is a 16MB limit for each document - detailed
here
If bigger than that you need to use GridFS.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
My question seems to be dump, but because i was studying this new technique, i've found that NoSql has changed from its beginning, for example, in the beginning there was the problem of see your own update, and for example Facebook dident let users to update their comments due to the write once, read many
So, do i change all concepts that i've read in 2010-2012 tutorials?
Has NoSql beat the CAP theorem ?
I agree this can easily turn into discussion. I'll give brief answers from my experience to your two questions:
No, the concepts haven't changed. The landscape seems to be growing quite a bit as lots of companies get into the NoSQL space. Beware vendor promises!
No way. Just read this article this morning, it is a great explanation on some of the issues with the CAP theorem: http://codahale.com/you-cant-sacrifice-partition-tolerance/
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
Can you please help to choose from Coredata or sqlite ??
Which one is better ? As I have complex query in database.
This blog will help you a little
http://blog.mcohen.me/2010/06/19/why-i-chose-sqlite-instead-of-core-data/
The answer, of course, is that "it depends". They both have their advantages and disadvantages depending on what you want to achieve.
Check out this article, and others, on choosing between the two: http://answers.oreilly.com/topic/1959-when-to-use-sqlite-instead-of-core-data-on-the-iphone/
Sqlite is a RDMS system and involves SQL and while CoreData is a object-oriented programming within xcode.. Both deal with a lot of data in the database. Both have their own way of writing and saving to the database. You need to know their specific ways... On deciding on which to use, it really depends on the circumstance you are in.. If you are using a simple query or have very little data in the database, you could use plist or userdefaults. The choice is yours because you know best what you need...
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
We have requirements that force us to have two layers of databases. A good caching solution backed by large distributed database. We are thinking to use redis for fast read and write. We are not yet settled for the database at backend, however we would prefer it to have following properties:
consistent over time.
robust (no data loss).
reasonably fast read.
distributed.
We are exploring cassandra and Mongodb as our options. Hbase might be a option too. Kindly let us know your views/ current state of work. We are expecting some comparative analysis which could be like in http://kkovacs.eu/cassandra-vs-mongodb-vs-couchdb-vs-redis , but should be more upto date and can give us better insight. An example usecase could be like when someone post a comment in facebook. The comment is then visible to all its friends in real time.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
I'm planning to do my first facebook-app.
The core of the app would be to choose certain photos from your profile and show them to others users (of the same app). My background is more on the C++ side and low-level programming.
I want to know your suggestions for the following:
1- Which hosting do you suggest? I have read about google-app-engine and Heroku, however I am not sure which one fits best for a free plan until it grows to a significant number of users.
Heroku seems great for a beginner since they give you a sample code, but I am not sure about their databases and their scalability while being free. From here I understand that I have only 5 mb of databases for free which seems too little... right?.
And one more thing: I'm assuming is possible to show photos from others users directly from facebook without hosting it
2- Which framework and language do you suggest given the core of my app? It is not a sophisticated app, so I want to do it as fast as I can without many technical troubles.
Thanks in advance
I think Heroku is good choice for you. http://devcenter.heroku.com/articles/facebook