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?
If the device of this only SQLite. +storIO.
On the server without any difference, with some more work. For communication API.
annette12 answered on 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 :)
pearlie.May answered on 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