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 10 months ago.
Improve this question
I have been thinking of making a program to use in my company. I would like to store information in a (local) database and use this to keep track of the payments of my clients. I am most experienced in programming in Java. Do you have any suggestions for these databases?
I believe you are probably looking for SQLite. It is very light, basic, works with SQL,but doesn’t have any built in relational methods to link multiple tables together(JOINS, etc). As you mentioned you’ll be using Java, here’s the SQLITEJDBCPackage. Also, here’s a blog that can help you get started.
On the other hand, there is a wide variety of databases present in the market like:
RDBMS: MySQL, PostgresSQL
NoSQL: MongoDB(can run on cloud and locally), Neo4J
Time Series Database(If you storing IOT or time dependant data): InfluxDB
Cloud Databases(Might not be relevant to you since you want a local setup, but just to help you understand better): Firebase, Neo4J, MongoDB, AWS RDS, etc.
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 5 years ago.
Improve this question
This question is a little more generic, a brainstorm one. I'm about to develop a small website, and I still don't know if it’s better for me to store my “Text” (to fill Labels, Messages, etc) data on the Database or just on the frontend.
I know that for a fact, consulting the BackEnd Database is slower than just searching a specific file, but it’s also better to update the list later-on (when the website is developed) by just running a script.
I want to know some opinions, experiences, advantages and disadvantages about both.
Edit: For the technologies, i was thinking in using ExtJS with a Java Backend, I'm not quite sure about the BD yet.
Consider what data you are storing and the purpose of your website.
Advantages of front end storage: quicker
Advantages of database storage: more secure/structured
If your strings are sensitive then I would secure them in your database. Any client information, including "Text" data should be stored on the back end. If the strings are only relevant to you as the site owner then I don't see a problem with storing them on the front end.
Also perhaps specify which technologies you are using to build this site to get more specific responses.
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 6 years ago.
Improve this question
For a small start-up mobile app/website what options are there for storing its data? I.e. Physical server or cloud hosted data base such as azure.
Any other options or insight would be helpful thank you!
Edit:
For some background I'm looking at something that users could regularly upload data to and consumers could query to find results through an app or website.
I guess it depends on your work load and also on the your choice of data store. Generally, SQL based storage are costlier on cloud based solution due to the fact that those can be only vertically upgraded whereas no-sql ones are cheaper.
So according to me you should first decide on your choice of data-store, which depends on following factors:
The type of data; is your data structured or it falls under non-structured category?
Operations that you will perform on the data. Do you have any transactional use-cases?
Write/Read pattern; is it a read heavy use case or a write heavy one ?
These factors should help you decide on an appropriate data-store. Each database has its own set of advantages and disadvantages. The trick is to choose one based on your use cases and above mentioned factors.
Hope it helps.
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 7 years ago.
Improve this question
I'm currently building a Hybrid mobile app using ionicframework,angularjs and cordova,in my app i will need some data storage such as all users details.
What i'm trying to figure out is how to update the database for all users,for example if a new user signs up,he should be added to the database and everyone else should be able see his profile instantly,i'm thinking the database should be shared online instead of just updating the local database installed with the app,i'm currently using SQLite plugin to store such data but i'm not sure if it's the right choice for my case.
Does anyone know how to reach what i want ? i would appreciate any help.
Thanks.
Too many users then no point in storing and syncing. Creates more data inconsistency issues and resource consumption.
Online is the way to go.
If there is a subset of users whom u want to store information then thats an option.
Like watsapp stores and syncs information of those who are on your contact or chats only and not the whole watsapp db.
Thank you guys,after a lot of research,few days ago i decided to use Firebase,it's really powerful and works perfectly with angularJS and ionicframework which i'm using to build my app. I would really recommend it in situations similar to mine.
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 9 years ago.
Improve this question
I'm trying to figure out if http://docs.phonegap.com/en/1.2.0/phonegap_storage_storage.md.html can handle versioning, conflicts, etc. similar to CouchDB's capabilities.
I'm building a mobile app wherein friends can share data. This data will be manipulated (add, edit, delete) when the app is online or offline. During offline operations, the data changes will be stored locally -- and then sync to a central database when it goes online (and everyone else will sync to that central database).
Obviously, there will be versioning, conflicts, etc. issues. CouchDB supposedly handles this well. However, I want to know if PhoneGap's storage is sufficient for my needs. Will it work or not?
sqlite has plenty of power for this kinda stuff, though even localstorage is pretty powerful unless you are manipulating data with heavy javascript. I say try localstorage first as it's very very easy to handle.
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 7 years ago.
Improve this question
I am trying to design a data store implementation like SQLite, BerkeleyDB or CouchDB suitable for a small embedded computer platform. The main criteria is minimal bloat and simple API.
I could not find any products that fit my needs. SQLite is a tad too large and mimics relational databases. CouchDB has a good RESTful API but is bloated.
Basically my goals are:
Written in C.
Key-value model preferred over relational model.
RESTful web server and API.
I am struggling with designing the database backend. What's the best way to store the data? How do I organize it with minimal performance loss? How do other implementations tackle this (SQLite for example)? Is there any literature on this?
Thanks!
try the Qdbm suite (qdbm.sourceforge.net). It' the fastest and more flexible key/value store I've used. You can find a comparaison with other similar packages here:
http://qdbm.sourceforge.net/benchmark.pdf
If the store is read intensive, you can try also the CDB package from DJB.
Hope it helps!
Maybe Redis is what you need?