Would this be a replacement for Valkey in small scale?
PostgreSQL
The world's most advanced open source relational database
Project
- About (history)
- Docs
- Donate to PostgreSQL
- Wiki
- Planet PostgreSQL
- IRC
- Mailing lists:
- pgsql-announce
- pgsql-hackers (developers)
- pgsql-general
- pgsql-jobs
- User Groups
Events
- SEAPUG Summer BBQ, 6 July in Seattle
- SFBA PostgreSQL Meetup, 12 July
- Chicago PostgreSQL Meetup, 19 July
- PGDay UK 2023, 12 September in London
- PGConf 2023, 3-5 October in New York City
- PGDay Israel 2023, 19 October
- PGConf.EU 2023, 12-15 December in Prague
Podcasts
Related Fediverse communities
- c/SQL on programming.dev
- #sql on Mastodon
- #postgresql on Mastodon
Short answer, maybe. Until you specify your needs or use case it is very difficult to say.
In general, most if not all, benchmarks I have seen comparing Postgres to RAM key value stores has always had postgres coming significantly slower. If speed is the most important factor then likely no, you still need a key value store.
Also, you wrote "small scale", but even that can be ambiguous. Is it small scale because it is small, but you still need fast lookups? or is it "small scale" because it is a small setup and speed is not an issue?
It ultimately comes down to your needs and your appetite for having a second technology if you already have postgres. Sometimes, even if a second technology is better at something, the overhead of having the second technology may not be worth it.
Saving it for a read later on!
