We put a Redis server inside our runtime
encore.dev
We put a Redis server inside our runtime
1–10 of 16 posts
Re: We put a Redis server inside our runtime
#2> 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.
Re: We put a Redis server inside our runtime
#3> 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 me…
Yeah I agree completely, especially because Redis is one of the easiest things to set up. This feels like the wages of tokenmaxxing lol
Re: We put a Redis server inside our runtime
#4Rewriting 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?
Re: We put a Redis server inside our runtime
#5If 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!!
Re: We put a Redis server inside our runtime
#6If 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!!
> Reddit
Redis?
Re: We put a Redis server inside our runtime
#7> 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 me…
Yeah I agree completely, especially because Redis is one of the easiest things to set up. This feels like the wages of tokenmaxxing lol
There is a difference between easy to set up and not having to set up anything. It's an improvement in operational UX.
Re: We put a Redis server inside our runtime
#8[flagged]
Re: We put a Redis server inside our runtime
#9Earlier quoted context omitted.
Yeah I agree completely, especially because Redis is one of the easiest things to set up. This feels like the wages of tokenmaxxing lol
There is a difference between easy to set up and not having to set up anything. It's an improvement in operational UX.
There's a difference between easy to set up and (creating 25,000 lines of code to maintain so that we're) not having to set up anything.
I'd call it a net loss.
Re: We put a Redis server inside our runtime
#10[dead]