We put a Redis server inside our runtime

(encore.dev)

18 points | by eandre 2 days ago

3 comments

  • sudowood0 1 hour ago
    > 25,000 lines of Rust

    I'd really like to understand why they didn't just also have a small container for this running. The only reasoning given in the article is "another container to run and manage" which Docker compose, TestContainers, etc will make trivial.

    If a dev came to me and suggested we go this route I would need to seriously be convinced. They even explicitly call out this is only for local development meaning it's not like this was piggy-backing off of a secondary need for a Rust redis anyways. Insanity.

    • pram 1 hour ago
      Yeah I agree completely, especially because Redis is one of the easiest things to set up. This feels like the wages of tokenmaxxing lol
      • luckystarr 15 minutes ago
        There is a difference between easy to set up and not having to set up anything. It's an improvement in operational UX.
  • khurs 1 hour ago
    If you look at what CloudFlare did - when they were unhappy with Nginx, they re-wrote their own proxy in Rust, one wonders if this company could instead have 'porting' reddit, started afresh?

    Reddit is from 2009 so must have lots of technical debt over the years? and could have been an opportunity to start afresh? They may have have ended up with a better product!!

    • krallja 58 minutes ago
      > Reddit

      Redis?

  • sshine 1 hour ago
    Rewriting Redis in Rust sounds genuinely useful when you want to rely on it as a library.

    Maintaining byte-for-byte parity with newer versions of Redis sounds like being in debt; why not rely on your fork instead?