22 ms·
Short lived, high frequency/throughput data (most likely some kind of non-essential logging), that gets accumulated on an interval in a different database would
by okket 10y ago
Short 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.