Home/ Questions/Q 8564089
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-11T17:07:02+00:00

I would ask a semi-theorical question about web services and client-server architecture. I have

  • 0

I would ask a semi-theorical question about web services and client-server architecture.

I have a server with a database with about 50 tables. This server holds even one table which contains information about users associated with the clients.
Each client has associations with a subset of all data in db.

The defined architecture implies that each client (running on Android app) calling ,with a predefined frequency, a certain number of Web Services, fill the local database, creating a copy of all the tables residing on server sb, containing the only information related to the requesting client.

Furthermore, the data in db server side can change, so frequent synchronization is required.

Considering that the client application can be imaginated as a shop online application, so should be possible browsing through providers, articles, make a order,remove orders etc.

So, when I talk about fill the local database I mean store providers, articles, …that is, all information realated to the requesting client.

Can make sense fill the local database with this information?

I think that is more reasonable call a web service only exactly when the information is required, and not store information in local db.
So, synchronization is no more required.

Tall me what you think about ? thank you.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I know NOTHING about Android development, but have tons of experience with using web services and SOA.

    In my experience, especially when the client device has limited storage and processing power, all the business logic and data logic should be in the web services, and the client app used only for display and calling those services. How you implement that is something that we can’t answer for you. It’s different on every project.

    The only exception is when you absolutely have to have the app running while not connected. In that case, be sure you know your specific requirements, and be very dilligent to only persist at the client the data that you absoutely need, and only provide the business logic that you absolutely need while disconnected.

    (This helps to keep security simpler as well – lost or stolen devices are one of the highest sources of data breaches, so the less potentially sensitive data on the device the better.)

    I don’t know if that’s helpful, but I throught I’d throw it out there.

    • 0