Python中SQLite支持数据库远程访问吗？

使用自己的文件锁解决这个问题。

Multiple processes can have the same database open at the same time. Multiple processes can be doing a SELECT at the same time. But only one process can be making changes to the database at any moment in time, however.

SQLite uses reader/writer locks to control access to the database. (Under Win95/98/ME which lacks support for reader/writer locks, a probabilistic simulation is used instead.) But use caution: this locking mechanism might not work correctly if the database file is kept on an NFS filesystem. This is because fcntl() file locking is broken on many NFS implementations. You should avoid putting SQLite database files on NFS if multiple processes might try to access the file at the same time. On Windows, Microsoft's documentation says that locking may not work under FAT filesystems if you are not running the Share.exe daemon. People who have a lot of experience with Windows tell me that file locking of network files is very buggy and is not dependable. If what they say is true, sharing an SQLite database between two or more Windows machines might cause unexpected problems.

We are aware of no other embedded SQL database engine that supports as much concurrency as SQLite. SQLite allows multiple processes to have the database file open at once, and for multiple processes to read the database at once. When any process wants to write, it must lock the entire database file for the duration of its update. But that normally only takes a few milliseconds. Other processes just wait on the writer to finish then continue about their business. Other embedded SQL database engines typically only allow a single process to connect to the database at once.

However, client/server database engines (such as PostgreSQL, MySQL, or Oracle) usually support a higher level of concurrency and allow multiple processes to be writing to the same database at the same time. This is possible in a client/server database because there is always a single well-controlled server process available to coordinate access. If your application has a need for a lot of concurrency, then you should consider using a client/server database. But experience suggests that most applications need much less concurrency than their designers imagine.

When SQLite tries to access a file that is locked by another process, the default behavior is to return SQLITE_BUSY. You can adjust this behavior from C code using the sqlite3_busy_handler() or sqlite3_busy_timeout() API functions.

qlite应该是只是一个本地文件，API放在各个语言的开发包里了，它本身不具备C/S的网络功能。

见官方文档：
“ If you have many client programs accessing a common database over a network, you should consider using a client/server database engine instead of SQLite.”
如果一定想支持远程访问有这么几条出路：
1、换其他支持网络访问的数据库如MySQL。
如果坚持要用Sqlite
2、楼上所述，用网络文件系统，但是不建议。因为随机读写在NFS等系统上的性能都很成问题，而且稳定性堪忧。

3、用RPC等封装一下，如Thrift、XML-RPC等，Java的话还有RMI等直接可以搞起。

https://www.zhihu.com/question/20130288/answer/14085013