An important thing to consider on web-services using LiteSync is that the database connection must be kept open. So traditional CGI or PHP scripts will not work because Apache would spawn a new process for each request. The service must be kept running and the db open, ready to serve a request when it comes.
WSGI is a good candidate.
Other alternatives (without Apache) are FastAPI (Python), Node.js and Java servlets
For PHP there are Swoole, ReactPHP, PHP-FPM with persistent PDO and RoadRunner
Regarding configuration, you have 2 options:
- Use many processes, each with its own database replica.
Pros: serve requests in parallel, linear increase in performance with number of processes
Cons: 2 subsequent requests from the same client can fall on different processes, and they may not be synchronized exactly at the same point. So information that is present on one process/database may not have reached the other, causing discrepancies.
- Use a single process with many threads.
Pros: less disk usage, less network traffic (communication between nodes)
Cons: the access to the database is serialized. SQLite uses a mutex, so in practice this use case will have only 1 thread using the database at each given time.
It is not all bad news though, as the serialization is limited to sqlite3_ functions and each query generally will use many calls (1 prepare, many calls to step, many calls to retrieve column info, etc.) so the different threads will have interleaved calls to the db functions. The performance is better than using a single thread, just note that there is a limit, the performance increase is not linear.