Logtide is making Redis optional for its self-hosted logging platform, pivoting to a Postgres-first architecture. The developer argues that for many users on a $20/month VPS, a 200MB Redis instance is unnecessary overhead for background jobs. The new design defaults to PostgreSQL for caching and queuing, using SKIP LOCKED and UNLOGGED tables for performance.

The move addresses the "dependency tax" of running Redis for basic tasks. Logtide now supports three paths: a zero-dependency Postgres-only mode, a Valkey path, and the legacy Redis option. Valkey, a Linux Foundation fork of Redis 7.2.4, is presented as the open-source alternative after Redis's license change to RSALv2/SSPL. It's a drop-in replacement.

Benchmarks show Valkey is 2.7x faster than PostgreSQL for job queues, but the developer questions if that matters for background log rotation. The abstraction uses a provider-based system, allowing users to mix cache and queue backends. For small deployments, the simplicity of a single database often outweighs performance gains, while Valkey caters to higher throughput needs.