What are the advantages of carrying out a local application database on the remote(your) server?

There is a commercial application. There is a database included with the software. The database must be maintained in current status (entity: spare parts, devices, etc. etc.). Whether to make a DB on our server? What are the pros? It will help to protect your data? How to protect data? Whether to bother or write database local to the client, and just to update it? Why even take out the DB on your server? After all, if you want to merge data from a dB just ponimaut traffic and so on. Maybe there is something that I do not consider.
June 5th 19 at 21:58
1 answer
June 5th 19 at 22:00
At carrying out of the DB on the server, you need:
  • to maintain and support the infrastructure servers, choosing a place geographically optimally in relation to the customers
  • implement API for working with clients using HTTPS with authentication
  • implement API for clients to work with the server
  • to consider the application architecture so that the API server was not a narrow link in performance
  • to consider the synchronization mechanism
Well, this is understandable. And what are the pros of the decision of the removal of a DB on the server? What do we get, abandoning the local DB? Whether to make the database on the server, or leave it local? - Tyshawn_Nikolaus commented on June 5th 19 at 22:03
of the advantages:
  1. unified database: a single state of the data for all customers
  2. centrally updated or rolled back for all customers
  3. quick access to a centralized database locally if you need to perform an update without waiting for updates from clients


To make the transition to client-server - you need to decide for yourself.
Still have the hybrid option: a DBMS locally and on the server (shared data).

Plus local is that you can work in offline mode from the centralized database. - alfonso56 commented on June 5th 19 at 22:06

Find more questions by tags Databases