This applies to situations when lots of write requests are being made,
right? Otherwise, SQLite can handle lots of concurrent connections.
On Wednesday, May 4, 2011 7:40:18 AM UTC-5, bmbouter wrote:
>
> SQlite has issues with efficiently serving multiple database connections
> simultaneously.
You're probably right about using Postgres. Postgres is rock solid,
scalable, and easy to use.
I've recently had a need to create a bridge between PostgreSQL and SQlite.
Primarily because I use SQlite in my dev environments, but use PostgreSQL
in production. I have been planning to write someth
I'd recommend going the PostgreSQL route. I have a number of apps that use the
architecture where Postgres is running in a federated multi-master setup with
client side SQLite db used as local cache. Building a data sync service between
the two using django to ship models via a RESTishAPI deger
SQlite has issues with efficiently serving multiple database connections
simultaneously. It is still ACID compliant, but the performance can crawl
with multiple users. I think this has to do with the locking being
filesystem based. That being said it sounds like your db's would all be
used by in
4 matches
Mail list logo
