The fact that you are using compact db for the client imposes quite serious restrictions on the available options in this scenario.
Given the limitations and performance requirements you want, you might consider introducing a service-based endpoint to synchronize the tables you need. If your architecture allows this, then asynchronously it will significantly increase performance, but then again, it may not even be viable depending on your architecture.
Something else to consider is the use of web sockets, not standard HTTP connections for a web service, as mentioned above. This way you could synchronize clients in real time, as web sockets are real fully two-way connections in real time. The main catch with this is that you must either ensure that all clients are compatible with web sockets, or provide a return to emulate the connection to the web server using an emulation environment for clients that do not match the parameters.
Not sure if this helps.
source share