3 ms·
Well, with PostgreSQL everything works just fine. Read and write performance is amazing, and full text search returns instantaneous results. With SQLite, it’s
by kuschku 9y ago
Well, with PostgreSQL everything works just fine. Read and write performance is amazing, and full text search returns instantaneous results.
With SQLite, it’s basically useless.
- tracker1 9y agoIt really depends... I've worked on systems that PostgreSQL (or any SQL rdbms) wouldn't be able to keep up with. I've seen many others that would do fine with SQLite. It depends. In the end, it's a matter of testing. Also, with faster drive options (Optane and whatever is next), it could very well be a decent option. It all depends. Frankly, for logging, I'd lean towards elasticsearch (ELK) these days, which is about the most write heavy situation you're likely to see. Depending on the scaling Mongo, RethinkDB, ElasticSearch and Cassandra can all be better solutions than RDBMS. I'd still reach for SQLite or PostgreSQL first depending on the situation though.
- kuschku 9y agoSure, with optane it may work — but the usual usecase for SQLite is on the slowest SD cards or spinning HDDs you can imagine, where the user didn't want to spend time configuring postgres