Türker Yıldırım

redis

  • Redis 8, a year on, and nothing to report

    Note2 min read

    A major version upgrade in May 2025, after thirteen months of a pin, and twelve months of nothing happening. Writing down that nothing happened is the only way…

  • A cache key registered with what regenerates it

    Note2 min read

    A registry of cache keys, maintained by review, one year after the incident that produced it. The registry has drifted twice in a year and both times the…

  • Cache invalidation by version prefix, three years on

    Note1 min read

    A version constant in every cache key since 2022, and what three years of using it actually looked like. Seven bumps in three years is roughly the rate…

  • A compatibility suite retired after a year

    Note2 min read

    A monthly job comparing two servers, kept for thirteen months to preserve an option, and switched off once the option stopped mattering. The tests were the valuable artefact…

  • Redis 8 under AGPL, and unpinning a version

    Note2 min read

    The first of May, an open source release again, and a pin from April 2024 that could finally be removed. A decision record that enumerates triggers cannot anticipate…

  • What AGPL actually requires of an internal service

    Note2 min read

    A licence with a reputation, read rather than assumed, for a piece of infrastructure behind our own application. The obligation attaches to modification and to network interaction with…

  • A licence that came back, and the migration we had prepared

    Deep dive9 min read

    The first of May, an AGPL release, and a decision from April 2024 that can finally be closed — in the direction nobody planned for.

  • A cache that was a second database

    Deep dive10 min read

    A cache holding data that existed nowhere else, discovered during a restart. A flush that lost four hours of user preferences.

  • A licence change, and the fork we did not take

    Deep dive10 min read

    20 March, a licence change, and a fork announced within a week. A dependency that is no longer open source, in production, everywhere.

  • A cache with persistence turned on to hide a design problem

    Note2 min read

    Turning on persistence so a restart would stop losing data, which is treating the symptom of data that should not have been there. Persistence on a cache is…