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 have just started using neo4j to store data in a graph, i.e. friends of friends etc..
But now I need to store standard application configuration data. This isn't graph data really, its settings that the application will use to help it run.
Normally I would store this in a table in a RDMS or in a document in MongoDB.
Can I still store this data in neo4j ? or should I use another database to store it?
Is it beneficial to have 2 databases i.e. neo4j and mongodb ?? Pros and Cons?
Anybody done anything like this?
Thanks in advance
It's perfectly fine to store it in Neo4j, if it is not large binary data.
Then I'd store it in a blob storage and just store references to it.
If you have nested structures you can either decompose them into multiple nodes, use property prefixes or serialize them to a string (e.g. JSON).
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 5 years ago.
Improve this question
I have to decide on a NoSQL database for a web app that should keep track of the user input and update the corresponding record as frequent as possible. To think about the frequency: let's say a blank record is generated on start and it should update on every key-up event coming from the user.
The methods I have seen for this kind of work are:
Write-Ahead-Logging/Journaling for the user data (not like the internal data consistency methods like Journaling of MongoDB or Write-ahead logging of CouchDb): I don't know if it is even implemented for the user data or the current methods can be utilized for this purpose.
Versioning for MongoDB or a less implicit cell versioning way of doing it in Cassandra
I tended to use Cassandra at the beginning, but I want to know the best fit methods* to achieve that kind of a scenario.
In Cassandra frequent updates on a cell can (but must not) lead to problems with compactions (to be more specific, when updated data is flushed from memtables to sstables because of too many concurrent updates.
If you do not need this data persisted an in memory solution (or in addition to a database) could help, I used Hazelcast for this.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I am considering using mongo db (it could be postgresql or any other ) as a data warehouse, my concern is that up to twenty or more users could be running queries at a time and this could have serious implications in terms of performance.
My question is what is the best approach to handle this in a cloud based and non cloud based environment? Do cloud based db's automatically handle this? If so would the data be consistent through all instances if a refresh on the data was made? In a non cloud based environment would the best approach be to load balance all instances? Again how would you ensure data integrity for all instances?
thanks in advance
I think auto sharding is what I am looking for
http://docs.mongodb.org/v2.6/MongoDB-sharding-guide.pdf
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I want to make an app like Instagram but the problem is where to store all text and images data, I have used Instagram when there is no connectivity available then app will show the last feeds even when app is freshly openend (not from background). It uses core data or sqlite.
I came across a scaling presentation from instagram a little while back where they talk how they started, using what and then how they approached the challenges.
See the link: http://www.scribd.com/doc/89025069/Mike-Krieger-Instagram-at-the-Airbnb-tech-talk-on-Scaling-Instagram
Hope this helps.
It's not known what Instagram uses. Use whatever you feel most comfortable with. Anything is possible with any storage technology, although some might fit better than others. Also, regarding your question on "core data or sqlite", you can use Core Data with an SQLite database as a backend (way easier than accessing raw SQL). You can also use other backends with Core Data: binary and XML.