{"slug": "valkey", "name": "Valkey", "category": "databases", "category_name": "Databases", "description": "Open-source, BSD-licensed in-memory key-value data store forked from Redis.", "recommenders": 8, "commenters": 8, "warners": 0, "score": 7.141, "rising": -2.62, "first": "2026-01-22", "latest": "2026-06-22", "why": "HN commenters like Valkey as a compatible Redis replacement they switched to after the license change, citing trust in its maintainers, wide cloud-provider support, and lower costs.", "why_is_quote": false, "has_verdict": true, "sentiment": {"recommend": 8, "neutral": 0, "compare": 0, "warn": 0}, "spark": [0, 0, 1, 0, 1, 1, 0, 5, 0, 0, 0, 0], "listed": true, "loved": ["Redis compatibility", "Trusted governance"], "caveat": "Diverging from Redis", "short_quote": "discovered we were saving money on our AWS bill, and have no motivation to go back to Redis.", "icon": true, "domain": "valkey.io", "github_repo": null, "official_url": "https://valkey.io", "pricing": "open source", "aliases": ["Valkey"], "verdict": [{"text": "HN commenters like Valkey as a compatible Redis replacement they switched to after the license change", "cites": [{"id": 774609760, "item_id": 48413110, "url": "https://news.ycombinator.com/item?id=48413110", "by": "jillesvangurp", "date": "2026-06-05", "stance": "recommend", "quote": "We switched to Valkey two years ago. I haven't really looked back.", "excerpt": "We switched to Valkey two years ago. I haven't really looked back. I think both projects have done a lot of nice stuff since the split but it's not really impacting anything I use. The feature set was fine five years ago and I don't think we're using anything in Valkey that wouldn't work in Redis. There are probably a lot of projects that never switched over because they had no real need. But most of the cloud provid", "context": "deploys on AWS/Azure/GCP-style infrastructure", "use_case": "in-memory data store", "switched_from": "Redis", "story": "Redis 8.8: New array data structure, rate limiter, performance improvements"}, {"id": 774588704, "item_id": 48411794, "url": "https://news.ycombinator.com/item?id=48411794", "by": "atraac", "date": "2026-06-05", "stance": "recommend", "quote": "It's faster, cheaper and compatible.", "excerpt": "We use almost exclusively Valkey now, mostly because we host on AWS and Render, which both use Valkey. It's faster, cheaper and compatible. I'd consider Garnet too but I believe it doesn't support LUA(or didn't at the time we needed it).", "context": "hosts on AWS and Render", "use_case": "in-memory cache/datastore", "switched_from": "Redis", "story": "Redis 8.8: New array data structure, rate limiter, performance improvements"}, {"id": 778246576, "item_id": 48640411, "url": "https://news.ycombinator.com/item?id=48640411", "by": "tempest_", "date": "2026-06-22", "stance": "recommend", "quote": "when I say redis I mean Valkey at this point", "excerpt": "> Mature ops would be tracking cache hit ratios right? Sure, and sentry integrates well with redis in python which is what I use primarily with redis. I don't think memcached is bad, I just think its old and industry has moved to redis because it offers more while covering the previous use case. Calling redis fiddly is a mischaracterization. For many use cases I have not had to think more than 30s to setup redis. (al", "context": "Python developer", "use_case": "caching", "switched_from": "Redis", "story": "In Praise of Memcached"}, {"id": 774601008, "item_id": 48412563, "url": "https://news.ycombinator.com/item?id=48412563", "by": "stevoski", "date": "2026-06-05", "stance": "recommend", "quote": "discovered we were saving money on our AWS bill, and have no motivation to go back to Redis.", "excerpt": "We switched to Valkey after the Redis license kerfuffle happened, discovered we were saving money on our AWS bill, and have no motivation to go back to Redis. So we\u2019ve stayed with Valkey.", "context": "", "use_case": "key-value store on AWS", "switched_from": "Redis", "story": "Redis 8.8: New array data structure, rate limiter, performance improvements"}]}, {"text": ", citing trust in its maintainers, wide cloud-provider support, and lower costs.", "cites": [{"id": 774602240, "item_id": 48412640, "url": "https://news.ycombinator.com/item?id=48412640", "by": "lukaslalinsky", "date": "2026-06-05", "stance": "recommend", "quote": "I've switched to Valkey and I'm not really looking back.", "excerpt": "I've switched to Valkey and I'm not really looking back. I'm much more comfortable with those people maintaining the software.", "context": "", "use_case": "key-value store", "switched_from": "Redis", "story": "Redis 8.8: New array data structure, rate limiter, performance improvements"}, {"id": 747654179, "item_id": 46728386, "url": "https://news.ycombinator.com/item?id=46728386", "by": "maxpert", "date": "2026-01-22", "stance": "recommend", "quote": "I've moved away from Redis to Val-Key for same reason", "excerpt": "Disclaimer: I am author of Marmot https://github.com/maxpert/marmot so I will sound extremely bias. I have been asked multiple times on why I chose SQLite and not Turso. I've always responded people that I don't trust an open-source project once it's backed by a VC firm. I've moved away from Redis to Val-Key for same reason, and we have seen the Redis train-wreck in slow-mo. I hope at no point in future Turso ever en", "context": "", "use_case": "key-value store", "switched_from": "Redis", "story": "Turso is an in-process SQL database, compatible with SQLite"}, {"id": 774609760, "item_id": 48413110, "url": "https://news.ycombinator.com/item?id=48413110", "by": "jillesvangurp", "date": "2026-06-05", "stance": "recommend", "quote": "We switched to Valkey two years ago. I haven't really looked back.", "excerpt": "We switched to Valkey two years ago. I haven't really looked back. I think both projects have done a lot of nice stuff since the split but it's not really impacting anything I use. The feature set was fine five years ago and I don't think we're using anything in Valkey that wouldn't work in Redis. There are probably a lot of projects that never switched over because they had no real need. But most of the cloud provid", "context": "deploys on AWS/Azure/GCP-style infrastructure", "use_case": "in-memory data store", "switched_from": "Redis", "story": "Redis 8.8: New array data structure, rate limiter, performance improvements"}, {"id": 774601008, "item_id": 48412563, "url": "https://news.ycombinator.com/item?id=48412563", "by": "stevoski", "date": "2026-06-05", "stance": "recommend", "quote": "discovered we were saving money on our AWS bill, and have no motivation to go back to Redis.", "excerpt": "We switched to Valkey after the Redis license kerfuffle happened, discovered we were saving money on our AWS bill, and have no motivation to go back to Redis. So we\u2019ve stayed with Valkey.", "context": "", "use_case": "key-value store on AWS", "switched_from": "Redis", "story": "Redis 8.8: New array data structure, rate limiter, performance improvements"}]}, {"text": " Complaints are rare; one commenter notes it is starting to diverge from Redis", "cites": [{"id": 778246576, "item_id": 48640411, "url": "https://news.ycombinator.com/item?id=48640411", "by": "tempest_", "date": "2026-06-22", "stance": "recommend", "quote": "when I say redis I mean Valkey at this point", "excerpt": "> Mature ops would be tracking cache hit ratios right? Sure, and sentry integrates well with redis in python which is what I use primarily with redis. I don't think memcached is bad, I just think its old and industry has moved to redis because it offers more while covering the previous use case. Calling redis fiddly is a mischaracterization. For many use cases I have not had to think more than 30s to setup redis. (al", "context": "Python developer", "use_case": "caching", "switched_from": "Redis", "story": "In Praise of Memcached"}]}, {"text": ", and another uses Kafka instead for data that must persist for days or weeks.", "cites": [{"id": 762673907, "item_id": 47667119, "url": "https://news.ycombinator.com/item?id=47667119", "by": "roscas", "date": "2026-04-06", "stance": "recommend", "quote": "Redis (or valkey.io) is also amazing and very fast.", "excerpt": "Oh what a huge article and a good read. Thank you. Ok, let's go. Why people use Kafka? Because you can throw lava at it and it will eat it. RabbitMQ is also very good, don't have production experience on it, so I leave it for a specialist. Redis (or valkey.io) is also amazing and very fast. But for a tram system or any system that needs persistent record for a period of time, I use a Kafka cluster with minimum of 3 s", "context": "", "use_case": "", "switched_from": "", "story": "I Replaced Kafka, Redis, and RabbitMQ with One Tool \u2013 A Deep Dive into NATS"}]}], "praise": [{"label": "Redis compatibility", "summary": "Commenters say it works as a Redis replacement for the features they rely on.", "quotes": [{"id": 774609760, "item_id": 48413110, "url": "https://news.ycombinator.com/item?id=48413110", "by": "jillesvangurp", "date": "2026-06-05", "stance": "recommend", "quote": "We switched to Valkey two years ago. I haven't really looked back.", "excerpt": "We switched to Valkey two years ago. I haven't really looked back. I think both projects have done a lot of nice stuff since the split but it's not really impacting anything I use. The feature set was fine five years ago and I don't think we're using anything in Valkey that wouldn't work in Redis. There are probably a lot of projects that never switched over because they had no real need. But most of the cloud provid", "context": "deploys on AWS/Azure/GCP-style infrastructure", "use_case": "in-memory data store", "switched_from": "Redis", "story": "Redis 8.8: New array data structure, rate limiter, performance improvements"}, {"id": 774588704, "item_id": 48411794, "url": "https://news.ycombinator.com/item?id=48411794", "by": "atraac", "date": "2026-06-05", "stance": "recommend", "quote": "It's faster, cheaper and compatible.", "excerpt": "We use almost exclusively Valkey now, mostly because we host on AWS and Render, which both use Valkey. It's faster, cheaper and compatible. I'd consider Garnet too but I believe it doesn't support LUA(or didn't at the time we needed it).", "context": "hosts on AWS and Render", "use_case": "in-memory cache/datastore", "switched_from": "Redis", "story": "Redis 8.8: New array data structure, rate limiter, performance improvements"}, {"id": 778246576, "item_id": 48640411, "url": "https://news.ycombinator.com/item?id=48640411", "by": "tempest_", "date": "2026-06-22", "stance": "recommend", "quote": "when I say redis I mean Valkey at this point", "excerpt": "> Mature ops would be tracking cache hit ratios right? Sure, and sentry integrates well with redis in python which is what I use primarily with redis. I don't think memcached is bad, I just think its old and industry has moved to redis because it offers more while covering the previous use case. Calling redis fiddly is a mischaracterization. For many use cases I have not had to think more than 30s to setup redis. (al", "context": "Python developer", "use_case": "caching", "switched_from": "Redis", "story": "In Praise of Memcached"}]}, {"label": "Trusted governance", "summary": "Some switched over the Redis license change and prefer who maintains Valkey.", "quotes": [{"id": 774602240, "item_id": 48412640, "url": "https://news.ycombinator.com/item?id=48412640", "by": "lukaslalinsky", "date": "2026-06-05", "stance": "recommend", "quote": "I've switched to Valkey and I'm not really looking back.", "excerpt": "I've switched to Valkey and I'm not really looking back. I'm much more comfortable with those people maintaining the software.", "context": "", "use_case": "key-value store", "switched_from": "Redis", "story": "Redis 8.8: New array data structure, rate limiter, performance improvements"}, {"id": 747654179, "item_id": 46728386, "url": "https://news.ycombinator.com/item?id=46728386", "by": "maxpert", "date": "2026-01-22", "stance": "recommend", "quote": "I've moved away from Redis to Val-Key for same reason", "excerpt": "Disclaimer: I am author of Marmot https://github.com/maxpert/marmot so I will sound extremely bias. I have been asked multiple times on why I chose SQLite and not Turso. I've always responded people that I don't trust an open-source project once it's backed by a VC firm. I've moved away from Redis to Val-Key for same reason, and we have seen the Redis train-wreck in slow-mo. I hope at no point in future Turso ever en", "context": "", "use_case": "key-value store", "switched_from": "Redis", "story": "Turso is an in-process SQL database, compatible with SQLite"}, {"id": 774601008, "item_id": 48412563, "url": "https://news.ycombinator.com/item?id=48412563", "by": "stevoski", "date": "2026-06-05", "stance": "recommend", "quote": "discovered we were saving money on our AWS bill, and have no motivation to go back to Redis.", "excerpt": "We switched to Valkey after the Redis license kerfuffle happened, discovered we were saving money on our AWS bill, and have no motivation to go back to Redis. So we\u2019ve stayed with Valkey.", "context": "", "use_case": "key-value store on AWS", "switched_from": "Redis", "story": "Redis 8.8: New array data structure, rate limiter, performance improvements"}]}, {"label": "Cloud availability", "summary": "Commenters say cloud hosts such as AWS and Render offer Valkey.", "quotes": [{"id": 774609760, "item_id": 48413110, "url": "https://news.ycombinator.com/item?id=48413110", "by": "jillesvangurp", "date": "2026-06-05", "stance": "recommend", "quote": "We switched to Valkey two years ago. I haven't really looked back.", "excerpt": "We switched to Valkey two years ago. I haven't really looked back. I think both projects have done a lot of nice stuff since the split but it's not really impacting anything I use. The feature set was fine five years ago and I don't think we're using anything in Valkey that wouldn't work in Redis. There are probably a lot of projects that never switched over because they had no real need. But most of the cloud provid", "context": "deploys on AWS/Azure/GCP-style infrastructure", "use_case": "in-memory data store", "switched_from": "Redis", "story": "Redis 8.8: New array data structure, rate limiter, performance improvements"}, {"id": 774588704, "item_id": 48411794, "url": "https://news.ycombinator.com/item?id=48411794", "by": "atraac", "date": "2026-06-05", "stance": "recommend", "quote": "It's faster, cheaper and compatible.", "excerpt": "We use almost exclusively Valkey now, mostly because we host on AWS and Render, which both use Valkey. It's faster, cheaper and compatible. I'd consider Garnet too but I believe it doesn't support LUA(or didn't at the time we needed it).", "context": "hosts on AWS and Render", "use_case": "in-memory cache/datastore", "switched_from": "Redis", "story": "Redis 8.8: New array data structure, rate limiter, performance improvements"}]}, {"label": "Lower cost", "summary": "Switchers report lower costs, including a smaller AWS bill.", "quotes": [{"id": 774601008, "item_id": 48412563, "url": "https://news.ycombinator.com/item?id=48412563", "by": "stevoski", "date": "2026-06-05", "stance": "recommend", "quote": "discovered we were saving money on our AWS bill, and have no motivation to go back to Redis.", "excerpt": "We switched to Valkey after the Redis license kerfuffle happened, discovered we were saving money on our AWS bill, and have no motivation to go back to Redis. So we\u2019ve stayed with Valkey.", "context": "", "use_case": "key-value store on AWS", "switched_from": "Redis", "story": "Redis 8.8: New array data structure, rate limiter, performance improvements"}, {"id": 774588704, "item_id": 48411794, "url": "https://news.ycombinator.com/item?id=48411794", "by": "atraac", "date": "2026-06-05", "stance": "recommend", "quote": "It's faster, cheaper and compatible.", "excerpt": "We use almost exclusively Valkey now, mostly because we host on AWS and Render, which both use Valkey. It's faster, cheaper and compatible. I'd consider Garnet too but I believe it doesn't support LUA(or didn't at the time we needed it).", "context": "hosts on AWS and Render", "use_case": "in-memory cache/datastore", "switched_from": "Redis", "story": "Redis 8.8: New array data structure, rate limiter, performance improvements"}]}, {"label": "Speed", "summary": "Commenters describe it as fast.", "quotes": [{"id": 774588704, "item_id": 48411794, "url": "https://news.ycombinator.com/item?id=48411794", "by": "atraac", "date": "2026-06-05", "stance": "recommend", "quote": "It's faster, cheaper and compatible.", "excerpt": "We use almost exclusively Valkey now, mostly because we host on AWS and Render, which both use Valkey. It's faster, cheaper and compatible. I'd consider Garnet too but I believe it doesn't support LUA(or didn't at the time we needed it).", "context": "hosts on AWS and Render", "use_case": "in-memory cache/datastore", "switched_from": "Redis", "story": "Redis 8.8: New array data structure, rate limiter, performance improvements"}, {"id": 762673907, "item_id": 47667119, "url": "https://news.ycombinator.com/item?id=47667119", "by": "roscas", "date": "2026-04-06", "stance": "recommend", "quote": "Redis (or valkey.io) is also amazing and very fast.", "excerpt": "Oh what a huge article and a good read. Thank you. Ok, let's go. Why people use Kafka? Because you can throw lava at it and it will eat it. RabbitMQ is also very good, don't have production experience on it, so I leave it for a specialist. Redis (or valkey.io) is also amazing and very fast. But for a tram system or any system that needs persistent record for a period of time, I use a Kafka cluster with minimum of 3 s", "context": "", "use_case": "", "switched_from": "", "story": "I Replaced Kafka, Redis, and RabbitMQ with One Tool \u2013 A Deep Dive into NATS"}]}], "caveats": [{"label": "Diverging from Redis", "summary": "One commenter notes Valkey and Redis are starting to diverge.", "quotes": [{"id": 778246576, "item_id": 48640411, "url": "https://news.ycombinator.com/item?id=48640411", "by": "tempest_", "date": "2026-06-22", "stance": "recommend", "quote": "when I say redis I mean Valkey at this point", "excerpt": "> Mature ops would be tracking cache hit ratios right? Sure, and sentry integrates well with redis in python which is what I use primarily with redis. I don't think memcached is bad, I just think its old and industry has moved to redis because it offers more while covering the previous use case. Calling redis fiddly is a mischaracterization. For many use cases I have not had to think more than 30s to setup redis. (al", "context": "Python developer", "use_case": "caching", "switched_from": "Redis", "story": "In Praise of Memcached"}]}, {"label": "Not for persistence", "summary": "One commenter uses Kafka instead for data that must persist for days or weeks.", "quotes": [{"id": 762673907, "item_id": 47667119, "url": "https://news.ycombinator.com/item?id=47667119", "by": "roscas", "date": "2026-04-06", "stance": "recommend", "quote": "Redis (or valkey.io) is also amazing and very fast.", "excerpt": "Oh what a huge article and a good read. Thank you. Ok, let's go. Why people use Kafka? Because you can throw lava at it and it will eat it. RabbitMQ is also very good, don't have production experience on it, so I leave it for a specialist. Redis (or valkey.io) is also amazing and very fast. But for a tram system or any system that needs persistent record for a period of time, I use a Kafka cluster with minimum of 3 s", "context": "", "use_case": "", "switched_from": "", "story": "I Replaced Kafka, Redis, and RabbitMQ with One Tool \u2013 A Deep Dive into NATS"}]}], "who": [{"by": "tempest_", "context": "Python developer", "url": "https://news.ycombinator.com/item?id=48640411", "date": "2026-06-22"}, {"by": "jillesvangurp", "context": "deploys on AWS/Azure/GCP-style infrastructure", "url": "https://news.ycombinator.com/item?id=48413110", "date": "2026-06-05"}, {"by": "atraac", "context": "hosts on AWS and Render", "url": "https://news.ycombinator.com/item?id=48411794", "date": "2026-06-05"}], "tags": ["for Redis users", "for AWS users", "for caching"], "use_cases": ["key-value store", "caching", "in-memory data store", "key-value store on aws", "in-memory cache/datastore", "rebuilding hn"], "compared": [{"slug": "redis", "name": "Redis", "co": 8, "switched_from": 6, "switched_to": 0}], "makers": [], "threads": [{"url": "https://news.ycombinator.com/item?id=48382047", "title": "Redis 8.8: New array data structure, rate limiter, performance improvements", "mentions": 4}, {"url": "https://news.ycombinator.com/item?id=48638886", "title": "In Praise of Memcached", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=47662866", "title": "I Replaced Kafka, Redis, and RabbitMQ with One Tool \u2013 A Deep Dive into NATS", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=47402527", "title": "Ask HN: What tech stack would you pick to rebuild HN today?", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=46677583", "title": "Turso is an in-process SQL database, compatible with SQLite", "mentions": 1}], "sentiment_by_month": {"2025-11": {}, "2025-12": {}, "2026-01": {"recommend": 1}, "2026-02": {}, "2026-03": {"recommend": 1}, "2026-04": {"recommend": 1}, "2026-05": {}, "2026-06": {"recommend": 5}, "2026-07": {}, "2026-08": {}, "2026-09": {}, "2026-10": {}}, "quotes": [{"id": 778246576, "item_id": 48640411, "url": "https://news.ycombinator.com/item?id=48640411", "by": "tempest_", "date": "2026-06-22", "stance": "recommend", "quote": "when I say redis I mean Valkey at this point", "excerpt": "> Mature ops would be tracking cache hit ratios right? Sure, and sentry integrates well with redis in python which is what I use primarily with redis. I don't think memcached is bad, I just think its old and industry has moved to redis because it offers more while covering the previous use case. Calling redis fiddly is a mischaracterization. For many use cases I have not had to think more than 30s to setup redis. (al", "context": "Python developer", "use_case": "caching", "switched_from": "Redis", "story": "In Praise of Memcached"}, {"id": 774609760, "item_id": 48413110, "url": "https://news.ycombinator.com/item?id=48413110", "by": "jillesvangurp", "date": "2026-06-05", "stance": "recommend", "quote": "We switched to Valkey two years ago. I haven't really looked back.", "excerpt": "We switched to Valkey two years ago. I haven't really looked back. I think both projects have done a lot of nice stuff since the split but it's not really impacting anything I use. The feature set was fine five years ago and I don't think we're using anything in Valkey that wouldn't work in Redis. There are probably a lot of projects that never switched over because they had no real need. But most of the cloud provid", "context": "deploys on AWS/Azure/GCP-style infrastructure", "use_case": "in-memory data store", "switched_from": "Redis", "story": "Redis 8.8: New array data structure, rate limiter, performance improvements"}, {"id": 774602240, "item_id": 48412640, "url": "https://news.ycombinator.com/item?id=48412640", "by": "lukaslalinsky", "date": "2026-06-05", "stance": "recommend", "quote": "I've switched to Valkey and I'm not really looking back.", "excerpt": "I've switched to Valkey and I'm not really looking back. I'm much more comfortable with those people maintaining the software.", "context": "", "use_case": "key-value store", "switched_from": "Redis", "story": "Redis 8.8: New array data structure, rate limiter, performance improvements"}, {"id": 774601008, "item_id": 48412563, "url": "https://news.ycombinator.com/item?id=48412563", "by": "stevoski", "date": "2026-06-05", "stance": "recommend", "quote": "discovered we were saving money on our AWS bill, and have no motivation to go back to Redis.", "excerpt": "We switched to Valkey after the Redis license kerfuffle happened, discovered we were saving money on our AWS bill, and have no motivation to go back to Redis. So we\u2019ve stayed with Valkey.", "context": "", "use_case": "key-value store on AWS", "switched_from": "Redis", "story": "Redis 8.8: New array data structure, rate limiter, performance improvements"}, {"id": 774588704, "item_id": 48411794, "url": "https://news.ycombinator.com/item?id=48411794", "by": "atraac", "date": "2026-06-05", "stance": "recommend", "quote": "It's faster, cheaper and compatible.", "excerpt": "We use almost exclusively Valkey now, mostly because we host on AWS and Render, which both use Valkey. It's faster, cheaper and compatible. I'd consider Garnet too but I believe it doesn't support LUA(or didn't at the time we needed it).", "context": "hosts on AWS and Render", "use_case": "in-memory cache/datastore", "switched_from": "Redis", "story": "Redis 8.8: New array data structure, rate limiter, performance improvements"}, {"id": 762673907, "item_id": 47667119, "url": "https://news.ycombinator.com/item?id=47667119", "by": "roscas", "date": "2026-04-06", "stance": "recommend", "quote": "Redis (or valkey.io) is also amazing and very fast.", "excerpt": "Oh what a huge article and a good read. Thank you. Ok, let's go. Why people use Kafka? Because you can throw lava at it and it will eat it. RabbitMQ is also very good, don't have production experience on it, so I leave it for a specialist. Redis (or valkey.io) is also amazing and very fast. But for a tram system or any system that needs persistent record for a period of time, I use a Kafka cluster with minimum of 3 s", "context": "", "use_case": "", "switched_from": "", "story": "I Replaced Kafka, Redis, and RabbitMQ with One Tool \u2013 A Deep Dive into NATS"}, {"id": 758443907, "item_id": 47402744, "url": "https://news.ycombinator.com/item?id=47402744", "by": "mindcrime", "date": "2026-03-16", "stance": "recommend", "quote": "Spring Boot, HTMX, Postgresql, Valkey, Solr", "excerpt": "If I had to build it myself? Probably something like: Spring Boot, HTMX, Postgresql, Valkey, Solr", "context": "", "use_case": "rebuilding HN", "switched_from": "", "story": "Ask HN: What tech stack would you pick to rebuild HN today?"}, {"id": 747654179, "item_id": 46728386, "url": "https://news.ycombinator.com/item?id=46728386", "by": "maxpert", "date": "2026-01-22", "stance": "recommend", "quote": "I've moved away from Redis to Val-Key for same reason", "excerpt": "Disclaimer: I am author of Marmot https://github.com/maxpert/marmot so I will sound extremely bias. I have been asked multiple times on why I chose SQLite and not Turso. I've always responded people that I don't trust an open-source project once it's backed by a VC firm. I've moved away from Redis to Val-Key for same reason, and we have seen the Redis train-wreck in slow-mo. I hope at no point in future Turso ever en", "context": "", "use_case": "key-value store", "switched_from": "Redis", "story": "Turso is an in-process SQL database, compatible with SQLite"}]}