Are there any techniques or tools to work with SQLite on a medium size/traffic/concurrency DB environment?
|
SQLite is an embedded database and it is not intended to be used as a client-server. If you really want to you can use SQLitening. |
|||||||
|
As stated before sqlite is not a client-server application and it is not built for highly concurrent operations. Nevertheless you can "make it client-server", if you use ssh.
works. |
|||
|
No, SQLite doesn't present a network endpoint - it is only accessible via the filesystem. It does support concurrent access from multiple processes on the same machine but at a very coarse-grained level (DML locks an entire table). So you could have a dozen Apache httpd processes all with a SQLite database on the local disk open, all doing |
|||
|
You could hack something together using netcat, but I can't imagine it would be a very elegant solution. |
|||
|
You can use a service similar to dropbox. There self-hosted solutions. However, SQLite3 was not created for a client-server model. You'd be better of with other solutions which were developed ground-up by client-server model. |
|||
|