md3911027514

8 ms·

1.
Valkey is now outperforming Redis in benchmarks: 37% higher write throughput(andrewbaker.ninja)
4 points by md3911027514 8mo ago|0 comments
2.
by md3911027514 1y ago
Regarding the "Durable Queueing Tradeoffs", doesn't Kafka prove you can be both durable and highly performant?
3.
by md3911027514 1y ago
It’s interesting how self-reports of productivity can be wrong. For example a study from METR found that developers felt that AI sped them up by 20%, but it empirically it slowed them down by 19%. https://metr.org/blog/
4.
by md3911027514 1y ago
Well yes but with native annotations the linter you’re already using can do a lot of the type checking work so for many teams it’s not worth it to add Pytype or mypy
5.
by md3911027514 1y ago
Pytype was cool before Python type annotations became widespread. It seems to me like the industry is naturally moving toward native type annotations and linters and away from static analyzers like Pytype and mypy.
6.
by md3911027514 1y ago
Isn't Styra like a company of like 50-100 people? Seems like it'd be a bummer to be an employee at the company that gets left behind.
7.
by md3911027514 1y ago
I mean isn't lying bad? They literally made public statements saying they "will always remain BSD." https://redis.io/blog/redis-license-bsd-will-remain-bsd/
8.
by md3911027514 1y ago
https://redis.io/blog/redis-license-bsd-will-remain-bsd/
9.
by md3911027514 1y ago
By switch I mean that all new projects use Valkey instead of Redis, and we've invested hundreds of hours into those new projects. We've also tried stuff with the Valkey Glide client.
10.
by md3911027514 1y ago
By switch I mean that all new projects use Valkey instead of Redis, and we've invested hundreds of hours into those new projects.
11.
by md3911027514 1y ago
Why would PaaS providers switch back to offering Redis? They've clearly all already invested a lot in Valkey (AWS, GCP, Heroku).
12.
by md3911027514 1y ago
Our company made the switch over to Valkey, and we've invested hundreds of engineering hours into it already. I don't see us switching back at this point especially when it's clear Redis could easily pull the bait-and-switch
13.
by md3911027514 2y ago
That makes sense! Thanks for the clarification
14.
by md3911027514 2y ago
I'm having trouble in my head understanding how these workflows are actually executed in the open-source version. Are there workers somewhere? How do we provision those and scale those up and down?
15.
by md3911027514 2y ago
It's cool that there's a chat interface in addition to the PR's. I find that for most reviews a little bit of back and forth is helpful.
16.
by md3911027514 2y ago
this is super sweet for developers (or anyone else) who like to have granular control over their LLM set up - ability to edit system prompt - ability to change LLM temperature - can choose which model to use (open-source or closed)
17.
by md3911027514 5y ago
Fanbase | Software Engineers | Los Angeles or San Francisco | Full-time, Onsite | Apply below or by email: jobs@fanbaselabs.com Fanbase is building a more creative future—we're creating a better funding model for artists by enabling de
18.
by md3911027514 5y ago
Fanbase | Software Engineers | Los Angeles or San Francisco | Full-time, Onsite | Apply below or by email: jobs@fanbaselabs.com Fanbase is building a more creative future—we’re creating a better funding model for artists by enabling deeper,
19.
by md3911027514 5y ago
Fanbase | Software Engineers, Product Designers | Los Angeles or San Francisco | Full-time, Onsite | Apply below or by email: jobs@fanbaselabs.com Fanbase is building a more creative future—we’re creating a better funding model for artists