Android Question SQL-Lite : Client-Server alternative for Android etc.

SQLite database is made of a file (or 3 files). There is no server and you cannot access a remote file.

h725 said:

Hello everybody !

I would like to know if somebody has experience with one Android device running
the database and another android or ipad etc. device accessing this database from
outside. I tried to find some informations on the web - you mainly find the answer
that sqllite is primary for standalone installations. Do you have experience with this
task ?


Kind Regards
h725

Click to expand...

Why can't you access a REST server using HTTP? The server would be either on your LAN or a private web server or the Cloud. The back end would be any database you like. Your Android/iPhone would act as a remote client. You could have hundreds (thousands?) of Android devices accessing the RESET server at the same time.

@Erel
Is there any alternative to this ?
I would like to avoid a "big" windows or linux pc as server.
I think using mysql on a raspberry together with jRDC2 Server should go into
that direction.

@Widget: I obviously answered in the second when you posted your reply.

h725 said:

@Erel
@Widget: I obviously answered in the second when you posted your reply.

Click to expand...

No problem. Perhaps if you could explain what type of information you are sharing (text, images, video) the # of records and # of concurrent users etc, it may help someone propose a solution. Maybe you don't need MySQL? Have you considered having the android send the updated rows to the device using a web server running PHP or if you can batch the operations use FTP? Because of security concerns most remote clients do not access the host database directly and insist on using an intermediary server.

I have used MySQL on Windows and it requires a large amount of resources (CPU, memory and disk space) compared to SQLite. I doubt it will run well on a Raspberry if at all. You will likely get better efficiency from an efficient fast server with SQLite as a backend database. If most of the users are reading from the database then SQLite may work well because it won't need table locks. But if most people are writing to the database then you may be looking at a limit of 10-20 concurrent users because of table locking contentions. This of course depends on the amount of data each user is writing.

So if you could post what you are trying to accomplish, I'm sure you'll get a better answer from the forum.

95 % of the information is text. In that case, maybe 10 users are the maximum.
"You will likely get better efficiency from an efficient fast server with SQLite as a backend database."
That sounds nice, do you have anything prepared or do you know a project in the WorldWideWeb goes in that direction ?

In the past I would have written one in Delphi.

But this looks interesting: https://www.b4x.com/android/forum/threads/b4x-cloudkvs-synchronized-key-value-store.63536/#content

Check the HttpServer library: Embed an Http Server in your Android Application

Thanks very much for this huge input. I will go through the articles.