Best Database to for a mobile application

Guca

Active Member
Joined
Jun 1, 2015
Messages
80
Reaction score
8
Hi Guys

I want to develop a mobile app that will store data (eg GPS coordinates etc) and users must be able to access that data on the mobile app itself, 1) I want to know what is the best and quicker database to use?. 2) what is the storage capability for whatever database that you suggest ?
 
What platform are you targeting?

Why not have the database elsewhere that is accessible via SSL Webservice calls?

Does the data need to be kept on the users device?
 
What platform are you targeting?

Why not have the database elsewhere that is accessible via SSL Webservice calls?

Does the data need to be kept on the users device?

Hi Necropolis

the platform i am targeting initially is android then apple at the later stage, the data doesn't have to be stored on the user's device it can be on a centralized server somewhere and another side question i would ask as well would be can the app be hosted on the cloud i don't have much experience with that as this will be my first app so the basics for it i know nothing about like how to get the app to be on the play store etc
 
Hi Necropolis

the platform i am targeting initially is android then apple at the later stage, the data doesn't have to be stored on the user's device it can be on a centralized server somewhere and another side question i would ask as well would be can the app be hosted on the cloud i don't have much experience with that as this will be my first app so the basics for it i know nothing about like how to get the app to be on the play store etc

Well it's your choice really - you could build a native app that targets Android and then apple - or you could create a mobile website that is optimised to run on all your target platforms.

That way your app can be hosted in the "cloud".

You might want to flesh out the basics before getting down to any serious dev work.
 
I response to the questions you raised in the first post:
1)There is no 'best' database option: it depends on the data, the structure of the data (relational or object?), the size of the data etc. There is no one shoe fits all database.
2) Regarding "storage capability" that is dependant on the environment that the database will be hosted on. But modern databases can store a hell of a lot of data. You can google the limits.

My thoughts:
Seeing as you are not an "expert" how about using something like Orchestrate, let them manage your database and you just use the REST API. Another option might be Firebase. both these options can become expensive though.

If you want to have more control, you could setup an API and the database yourself. (this has a strong learning curve however).
As an example:
- you can use Loopback for the API
- Mongo DB(as the database connected to the API)
- And whatever client you want all using the API for data persistence and retrieval

If you want to play around with this , one can setup the database using Modulus and run the API on Openshft (Both have free options available)

Both these options will allow an app or website to access the data from a single point (i.e. the API).

You should also note that there are many security concerns when setting this up yourself. So I would recommend you take the managed route rather then the setup yourself route (as this is your first app).

You might want to flesh out the basics before getting down to any serious dev work.
This is an extremely valid point, don't just jump into the deep end. Take your time and do proper research. Don't merely use (as an example) Mongo as your database just because I used it in my example. Choose the database that best fits your need/budget. There are many databases you could choose from (from relational to noSQL) that could work for you e.g. PostgreSQL , Mongo, My SQL , Amazon RDS , Couchbase etc.

Hi Necropolis
the platform i am targeting initially is android then apple at the later stage, the data doesn't have to be stored on the user's device it can be on a centralized server somewhere and another side question i would ask as well would be can the app be hosted on the cloud i don't have much experience with that as this will be my first app so the basics for it i know nothing about like how to get the app to be on the play store etc
Why dont you write in full sentences / use proper language (e.g. I instead of "i"). Why should I take time to help you / reply, if you cant even take a few seconds to write proper sentences when asking for help?
 
Last edited:
I response to the questions you raised in the first post:
1)There is no 'best' database option: it depends on the data, the structure of the data (relational or object?), the size of the data etc. There is no one shoe fits all database.
2) Regarding "storage capability" that is dependant on the environment that the database will be hosted on. But modern databases can store a hell of a lot of data. You can google the limits.

My thoughts:
Seeing as you are not an "expert" how about using something like Orchestrate, let them manage your database and you just use the REST API. Another option might be Firebase. both these options can become expensive though.

If you want to have more control, you could setup an API and the database yourself. (this has a strong learning curve however).
As an example:
- you can use Loopback for the API
- Mongo DB(as the database connected to the API)
- And whatever client you want all using the API for data persistence and retrieval

If you want to play around with this , one can setup the database using Modulus and run the API on Openshft (Both have free options available)

Both these options will allow an app or website to access the data from a single point (i.e. the API).

You should also note that there are many security concerns when setting this up yourself. So I would recommend you take the managed route rather then the setup yourself route (as this is your first app).


This is an extremely valid point, don't just jump into the deep end. Take your time and do proper research. Don't merely use (as an example) Mongo as your database just because I used it in my example. Choose the database that best fits your need/budget. There are many databases you could choose from (from relational to noSQL) that could work for you e.g. PostgreSQL , Mongo, My SQL , Amazon RDS , Couchbase etc.

Why dont you write in full sentences / use proper language (e.g. I instead of "i"). Why should I take time to help you / reply, if you cant even take a few seconds to write proper sentences when asking for help?

Sorry about my sentences :cry: ( Nerves getting the better of me) being new here is not easy. Thanks for the info though
 
1. An Azure database.
2. Scales as your data grows. The minimum will be about 20MB.

//Trying really hard to be straight to the point.
 
Most of the well known dbms's will be fine for backend work. SQL Server, MySQL, Oracle, DB2. Use sqllite to store data on the device.

I would choose the backend dbms based on the OS on which the server would run.
Windows = SQL Server
Linux = MySQL
Unix = Oracle

Any of the OS's are fine. Choose the one you know and have the most experience with and base your tech stack on that. Remember thought at some point you become tied to it. It becomes too expensive to change. Look at the skills of the people who work for you and make a choice on that basis. Its very expensive re-skilling.
 
If you need your app to run in remote areas without 3g I would go for a local DB which syncs when it has the opportunity otherwise go with a web service.
 
Hi Guys

I want to develop a mobile app that will store data (eg GPS coordinates etc) and users must be able to access that data on the mobile app itself, 1) I want to know what is the best and quicker database to use?. 2) what is the storage capability for whatever database that you suggest ?

I would suggest a REST Web API with a SQL Backend Database. If your data is going to be really huge then Oracle is your best bet for db.

You can write your front-end and consume API in Xamarin which you can compile to Android or iOS.
 
Top
Sign up to the MyBroadband newsletter
X