3 ms·
I've been using Postgres for the past 20 years, and it's basically almost always been the right choice. Even when it's not, it's a good starting point to explo
by davidw 10y ago
I've been using Postgres for the past 20 years, and it's basically almost always been the right choice. Even when it's not, it's a good starting point to explore the problem until everyone's really, really sure that something else might be best for that niche.
- okket 10y agoShort lived, high frequency/throughput data (most likely some kind of non-essential logging), that gets accumulated on an interval in a different database would be such a case. Something like Redis can be the right choice there. Also PostgreSQL is much more than a SQL database, it rivals an application server with its flexibility through extensions and supported languages.
- davidw 10y agoYes; antirez originally created redis with a logging thing in mind if memory serves... Indeed: https://groups.google.com/forum/#!msg/redis-db/DHBqQ7x4sOU/eH_2nB2RNiMJ https://groups.google.com/forum/#!msg/redis-db/DHBqQ7x4sOU/e...
- ralusek 10y agoIf memory serves? Redis serves everything directly from memory.
- jimktrains2 10y agoYes, but it has Append Only Files (AOF) that are similar to postgres' WAL and allow it to be durable. It can also fork periodically and write a copy of the database to disk. (It's single threaded and linux will COW when forking so it's safe and efficient iirc.)
- fulafel 10y agoPG offers unlogged tables for non-acid ephemeral data.
- deleted 10y ago[deleted]