Show HN: I created Redis alternative in Go that even runs natively on Windows

A backend developer created FrostDB, a Redis-compatible database written in Go that runs natively on Windows, supporting commands like GET/SET, Pub/Sub, Streams, and GEO with RDB import/export. The project aims to eliminate the need for VMs or Docker to run Redis on Windows, targeting development and testing use cases.

Hi I am a backend developer for almost a decade and mostly work on Windows servers; when it comes to deploy the internal tools and web application. For redis we have to spin a another VM in hypervisor just to run Redis. For local development I have to install heavy ass docker desktop or run a parallel operating system WSL just to run teeny tiny redis server. Some alternatives exist already such as godis but they only cover partial redis surface I have been trying to create redis fork that runs nativerly on Windows but for a single person it's a herculean task. So i have been taking help of various coding agent and ai models to come up with something that can help run be run natively on Windows so I can run redis-py and arq and huey like libraries with ease. So here it is: FrostDB. It's a single binary that currently implements from basic GET/SET commands to Pub/Sub, Streams, Hashes, Lists, Sets, and GEO commands with RDB import/export, LRU eviction etc. It's compatible with many Redis client libraries across multiple programming languages, including those that use Redis as a message queue. The implementation of the supported commands is tested against the original Redis test suite from the Redis GitHub repository. I'm still testing a few things and am now shifting my focus toward performance. This isn't meant to replace Redis, and I'm not telling anyone to switch to it. But if you're looking for a Redis-compatible server that runs natively on Windows, something now exists, at least for development and testing. Comments URL: https://news.ycombinator.com/item?id=48884299 https://news.ycombinator.com/item?id=48884299 Points: 2 Comments: 0