What database to use for Android app?

Plan to create an app for Andoid (drug Reference).
What kind of database it is advisable to use for these purposes, if presumably drugs will be quite a lot?
Choose between SQLite, MySQL, Apache Derby, PostgreSQL
That you have chosen?
June 7th 19 at 15:41
3 answers
June 7th 19 at 15:43
If the device of this only SQLite. +storIO.
On the server without any difference, with some more work. For communication API.
June 7th 19 at 15:45
In General, the answer to this question depends heavily on the functionality of your app and what data and how much you plan to store in the database. Without this detail, the question turns out to be very common, the same can be expected response.

How much and what type of data you plan to store in the database?
If we are talking about several thousands of records, this can be stored in SQLite on the client side. If we are talking about millions of records, it is best to put on the server side. Is important also the type and weight of the data. If you plan to store only the texts, it is possible to store on the client side. If you have files there (for example, instructions to drugs) and images, such a database would weigh more and it is better to submit to the server.

If the functionality of your application does not involve great exertion or specific work with the data, then I would advise to stay on SQLite. Subjectively I have the impression that drug reference to use MySQL or PostgreSQL is from a gun on sparrows. In any case, if the project is "off", then you will re-write everything from scratch and carefully think through the architecture :)
Thank you for your answer. I agree with you. Yes, in fact, decided poproboval your skills in the field of Anroid Development. I decided that to start SQLite will be enough. Pictures beginrow to store on Local Storage. There was a version of the pictures also in the blob, but I want to the database was relatively quick. For starters, plan on approximately 1000 drugs and more. And then, as you said "if they fly", it probably will grow.
Do I understand correctly that if you store data on the server side, it's not possible to cache at the client? I.e. to give the customer the "offline" access to the database - rosario.Marv commented on June 7th 19 at 15:48
why not possible? Of course there are. Everything is in your hands :)
I'm not an Android developer, therefore, competent for the cache can not answer. Googling the topic of caching in Android, I am sure that this task is already solved. But at worst, nothing prevents you to create client-side database in which you would "cache" received from the server to provide to them offline access. However, then you have a number of tasks of type keep data in the cache, the priority loading data from cache, etc. - annette12 commented on June 7th 19 at 15:51
thanks again) - rosario.Marv commented on June 7th 19 at 15:54
June 7th 19 at 15:47
If start without problems - any ORM to help you. Google recommends Room, I personally prefer DBFlow.
If speed is important, but don't mind spending time in the proceedings - Realm. In terms of speed of application - Realm will run circles around even the native SQLite
Thank you. Something to explore at your leisure)) - rosario.Marv commented on June 7th 19 at 15:50

Find more questions by tags AndroidDatabases