Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
Is there any way to implement reactivity with other database such as PostgreSQL in meteor? We need to have live updates with databases other than MongoDB.
Currently (0.7.0.1), Meteor's only supported database is Mongodb which is very coupled with what is called Minimongo, a client side implementation that mimics the mongodb api and is what basically one of the core components that allow the magic behind Meteor's reactivity.
That being said, other (sql) databases are actually on Meteor's roadmap which you can follow on the Trello board at https://trello.com/c/6ugalZMG/54-additional-database-support and https://trello.com/c/Gf6YxFp2/42-sql-support
But currently, there are some third party initiatives such as the meteor-sql smart package on atmosphere which opens up the first opportunities to develop against SQL.
The full reactivity is what you need to handle, though. Since it is implemented using publish/subscribe/observe api's of meteor and actually don't care much about the underlying data structure. Mongodb is just there for general convenience, but you can implement just about anything as your reactive data source.
In fact this video tutorial from eventedmind takes you through the steps of creating a custom reactive data source.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed last month.
Improve this question
I am developing an app for keeping attendance records for the students and I am confused about using either SQFlite or Hive for the local database. What are the pros and cons of both? How does each perform in apps with smaller and more complex databases?
I am currently using Hive and it seems like a hassle regarding code readability.
if you want the saved data to be fetched instantly and you won't need complex queries or have relations among the saved entities then go ahead and use Hive since it loads its boxes (saved data) in the memory for instant fetching
otherwise use SQFlite as it's more readable, scalable, and customizable.
in your case and regarding the project you are working on, I believe you should go with SQFlite, maybe in the future you will add some other features not just attendance, and might need to make complex queries.
Both of them work great, but for both proper data modelling is essential.
However, I wonder whether your app can work without storing data externally. In that case, neither is a good option.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 2 years ago.
Improve this question
I'm new to Swift and I'm building on a simple app that relies on login/sign up functions for each user. When I wanted to learn about databases in Swift, I came across Core Data and from what I understood it's like cookies/cache that stores data in the user's phone. If that's so, what's the best way to connect the app to a regular database like SQL?
Core Data is an ORM (object-relational mapping) system. Overly simplyfied you build your data model entities and and relationships between them and Core Data cares about the rest. Under the hood it uses an SQLite database by default, but it also can handle other types of storage (e.g. binary or XML).
To answer your question, for Login/Signup purposes you should look into storing user data such as auth tokens etc. in the Keychain.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I already have a .Net Web project running on MongoDB where I store some news/feed data.
After a while I needed a faster way to track "who shared what" and "how to find relationships depending on these information".
Then I came up with an idea to use graphDB to track related feeds and users.
Since the system is already running on MongoDB, I am thinking of leaving the data in Mongo and creating the graph representation in Neo4J for applying a graph search.
I do not want to migrate all my data to Neo4J because many people telling me MongoDB's I/O performance is way better than Neo4J and they also pointed out Sharding feature.
What would you suggest in this situation?
And If I follow my idea, will it be a good practice?
Personnally I think there are no unique answer and best practices. It is common usage to use polyglot persistence systems.
Now everything is based on your context and there are points we can't just reply for you :
How much time do you have (learning a new technology is not a matter of days until you can use it in production and sleep good )
How much money you can invest in the project , sharding is, AFAIK, a neo4j enterprise feature and licenses have a cost if you're not opensource or commercial company. Also hosting costs for Neo4j in cluster mode.
How much data ? As long as your graph can fit in memory, you'll not run I/O issues.
Now, away from these points, yes you can in a first instance trying to map neo4j on top of mongoDB.
Maybe try to do incremental migrations, and at then end of the process, maybe ask you the following questions, WHY do you need MongoDB to handle graph structures ?
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I am trying to learn NoSQL, and am implementing that in a project I am working on now as a means to pick it up. I understand there are no hard rules around it. But I'd be happy to read on some of the following:
Guidelines on how to structure a NoSQL document.
Moving from a RDBMS to a NoSQL thinking.
Difference between storing data in a NoSQL to that from RDBMS
Thanks!
I do have previous experience in RDBMS, and have been working with them for years.
Every concept will require to learn new thinking. Your question is to general for a specific
answer.
You will structure and work with CouchDB documents in another way as with MongoDB documents. In CouchDB you will do queries with MapReduce. In MongoDB you have a flexible query interface similar to a RDBMS.
A Key-Value store requires a completely new way of thinking. You have to know your query patterns before you are able to structure your content the right way. You have no index, so you have to build your own structure.
One blog that gives a lot of NoSql information is http://nosql.mypopescu.com
Update
The Riak people have some interresting questions too:
Will my access pattern be read-heavy, write-heavy, or balanced?
Which datasets churn the most? Which ones require more sophisticated conflict resolution?
How will I find this particular type of data? Which method is most efficient?
How independent/interrelated is this type of data with this other type of data? Do they belong together?
How much will I need to do online queries on this data? How quickly do I need them to return results?
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
As I am starting a new product development in Windows Form C#.Net Application, I want to use Mongo DB with it.
Could anybody please let me know that can I use MongoDB database for Windows Form application ? and if yes, How about the reports (complex reports) and relation with them?
As I am new to MongoDB, I don't have any idea to integrate reports and relation with it.
Please let me so I can go further and take decision about database choice.
Thanks in advance.
You can use MongoDB database for Windows Form application. Store your reports information in MongoDB's native BSON documents. For example each BSON document will stores one report. Use ids of documents for relations. As i found samus C# driver is fine. Check it;)
I am not sure I understand your question. You tagged it with mongodb-csharp, so you already seem to know there is a driver available for C# under Windows (which is also quite obvious if you check out the mongoDB page's driver section), so: yes, you can use mongoDB in a C# Windows application - there are even several other drivers available, like the "official" C# driver or NoRM.
That being said, reporting is often considered to be a weakness of NoSQL databases, which is true if you need to aggregate data via complex queries. You might want to store data needed for reports in an "old-fashioned" relational database.