kaliades

5 ms·

1.
Show HN: BetterDB, MIT Valkey-native context layer for AI agents(github.com)
5 points by kaliades 3mo ago|0 comments
2.
Show HN: An agent that tunes its own cache
7 points by kaliades 4mo ago|0 comments
3.
by kaliades 5mo ago
BetterDB ( https://betterdb.com ) ( https://github.com/BetterDB-inc ) | Founding Engineer | Remote | Full-time BetterDB is building the tooling ecosystem for Valkey, the high-performance Redis fork backed by AWS, Go
4.
Show HN: Agent cache for Valkey, now in Python with bundled LiteLLM pricing(pypi.org)
1 points by kaliades 5mo ago|0 comments
5.
by kaliades 5mo ago
Exact match, word for word. agent-cache takes everything that defines an LLM request - which model you're calling (gpt-4o, Claude, etc.), the full conversation history (system prompt + user messages + assistant responses), sampling par
6.
by kaliades 5mo ago
It caches AI agent operations in Valkey (or Redis) so you don't repeat expensive work. Three tiers: if your agent calls gpt-4o with the same prompt twice, the second call returns from Valkey in under 1ms instead of hitting the API. Sam
7.
Show HN: Agent-cache – Multi-tier LLM/tool/session caching for Valkey and Redis
18 points by kaliades 5mo ago|5 comments
8.
by kaliades 6mo ago
I completely understand your point and have had similar feelings when I've applied to previous companies. There are 2 points I can make to try and make it make sense (a lot of makes...) 1 - The moment a job post goes live, there are hu
9.
by kaliades 6mo ago
The simplest approach is the best in 90%+ of the cases!
10.
by kaliades 6mo ago
Thank you!
11.
by kaliades 6mo ago
That's exactly the bet we're making. The Redis/Valkey ecosystem has enough sprawl - a tool that does one thing well and stays out of the way is what we'd want to use ourselves.
12.
by kaliades 6mo ago
BetterDB ( https://betterdb.com ) ( https://github.com/BetterDB-inc ) | Founding Engineer | Remote | Full-time BetterDB is building the tooling ecosystem for Valkey, the high-performance Redis fork backed by AWS, Go
13.
BetterDB – open-source Redis/Valkey migration across clouds and self-hosted
15 points by kaliades 6mo ago|6 comments
14.
Show HN: Valkey-native semantic cache with OTel and Prometheus built in
4 points by kaliades 6mo ago|1 comments
15.
Show HN: Let AI agents debug your Valkey/Redis(npmjs.com)
2 points by kaliades 6mo ago|0 comments
16.
by kaliades 7mo ago
Thank you, I'll keep that in mind! That's one thing I like in OSS projects, people share their pain points freely. Also, that's why I organize things into projects inside Claude (not code) for keeping things separated and org
17.
Show HN: Valkey-powered semantic memory for Claude Code sessions
2 points by kaliades 7mo ago|1 comments
18.
Show HN: BetterDB Cloud – monitor Valkey/Redis in VPCs with a lightweight agent
4 points by kaliades 7mo ago|0 comments
19.
by kaliades 7mo ago
Update: we've filled this role. Thanks to everyone who applied — and especially to those who actually ran the product. We'll be hiring again soon!
20.
Show HN: BetterDB – Valkey/Redis monitoring that persists what servers forget
4 points by kaliades 7mo ago|0 comments
21.
by kaliades 7mo ago
BetterDB ( https://betterdb.com ) ( https://github.com/BetterDB-inc ) | Founding Engineer | Remote | Full-time BetterDB is building the tooling ecosystem for Valkey, the high-performance Redis fork backed by AWS, Go
22.
by kaliades 8mo ago
They're still wire-compatible for core commands, so most existing code works with both. The main differences so far: - New features diverging: Valkey added COMMANDLOG for query analysis, per-slot cluster metrics. Redis just shipped Ve
23.
by kaliades 8mo ago
I remember Vector Sets - I helped Rowan with the vector-sets-browser. Exciting to see you back working on Redis. Would love to hear more about the new data type when you can share. And yes, it is normal for different projects to take on dif
24.
by kaliades 8mo ago
Comment: Since the fork, Valkey and Redis have been diverging, especially with the latest releases - new features like COMMANDLOG, per-slot metrics, and different optimization paths. Existing Redis extensions might connect to Valkey, but th
25.
Show HN: First Valkey-specific VS Code extension (open source Redis fork)(github.com)
2 points by kaliades 8mo ago|7 comments
26.
by kaliades 8mo ago
Thanks! Those are exactly the right questions. 1. Cardinality: We don't do per-key metrics — that's a guaranteed way to blow up Prometheus. All pattern metrics are aggregated at the command pattern level (e.g., HGETALL user:* not
27.
Show HN: BetterDB – OSS Valkey/Redis monitoring with historical data
6 points by kaliades 8mo ago|1 comments
28.
by kaliades 2y ago
Thank you! I am thinking of also making a chrome extension, if people are finding it useful to directly inject that stat next to the company name in LinkedIn jobs, wework remotely, and so on.
29.
by kaliades 2y ago
My goal is not to get a job but to create a sort of listing that people can use to see how much the company they have applied to has been flagged over time. In terms of successful interactions glassdoor and such do a much better job of keep
30.
Tired of getting ghosted by companies? Let's call them out together(ghostedby.club)
14 points by kaliades 2y ago|14 comments

More ›