Renaming thread about valkey HOT 135 CLOSED

Redis came from Remote Dictionary Server... so maybe Open Dictionary Server -> Odis

from valkey.

Radish 😁

from valkey.

openkvs

from valkey.

openkv

from valkey.

Redis 🔴

Blueis 🔵

from valkey.

Redict was a good name. We'll have to relate to them (the new LGPL fork) since they'll be part of the landscape, at least initially. Independent clients from now on might more officially target all of KeyDB, Redict and others. The name is good, since it's not r*dis, yet similar enough so people understand what it is.

You could just come work with us and get used to the idea of copyleft 😉

from valkey.

Rodis (like redis but with an O like in Open Source)

from valkey.

CampoKV, because Salvatore was born in Campobello di Licata.

from valkey.

bluewas

from valkey.

oops-i-redis-again
re-redis

from valkey.

TARDIS? (May only appeal to old time Dr Who fans). This store is so much bigger than it appears at first glance.

from valkey.

KV Wentworth - Fast Cache Now!

I think the one positive out of all of this. There are going to be so many random memes in our docs referencing all the names we didn't pick. I'm sure there are going to be random radishes on our website and just some random collection of folks will know why.

from valkey.

bluedis

from valkey.

Retardis

from valkey.

DynamoKV

from valkey.

Greenis

from valkey.

"KV" is likely selling this project short IMO. I also feel that we should move on from "*dis". What happened has happened. Let's move on and build something amazing with a clean image for the community. There are plenty of other options to connect with the former Redis community members/users.

from valkey.

Odis (Open Dictionary Server)

from valkey.

just an reverse order of Redis: Sider

from valkey.

I don't know why I kind of like the name "placeholderkv".

Can we call it "keyholder"? It kind of describe what it does: holder lots of keys (and their values) for you.

from valkey.

For the record, there are already a few kiwis:

• pikiwidb "a high-performance, large-capacity, multi-tenant, data-persistent, strong data consistency based on raft, Redis-compatible elastic KV data storage system based on RocksDB"
• 云数据库 TencentDB for KeeWiDB

If kiwi (in one form or the other) already means redis-like database, then isn't this a perfect name for us? I.e. OpenKiwi

Compared to keyvii, keewee, kv, keyvi, I think kiwi is more catchy and easy to spell. There is even an emoji for it. 🥝

from valkey.

OpenCache

from valkey.

This could get... confusing with "kiwi" (an image build tool). I would appreciate it if we didn't do that. :)

from valkey.

Whodis
Newdis

from valkey.

You could just come work with us and get used to the idea of copyleft 😉

There may be some really good reasons for this developer community to consider copyleft. But I think that it is a lot to ask the existing community that was working on the core Redis engine to make such a significant policy decision overnight, without coming to a consensus as a community on the matter. This is a group that just had a huge unilateral change in license disrupt their lives and plans. Let's give them a little space to move forward as a community?

A vibrant BSD-3 licensed project will benefit you in yours, since you will be able to incorporate their improvements into your own copy. Of course the reverse isn't true. That would be quite like how Linux can integrate improvements from FreeBSD, but not the other way around.

Since this a thread on naming, not the license, I will try to make this the last comment I'll make on the subject in this thread.

from valkey.

@Conan-Kudo @ddevault Let's move the discussion to a more appropriate issue, either #8 or make a new one. If we keep commenting here I'm going to start deleting messages.

from valkey.

In the spirit of AI, I asked Gemini Advanced. Maybe this list further helps some of the creative juices?

Suggest alternatives to the open source product name Redis

Absolutely! Here's a breakdown of some alternative names for a Redis-like product, along with the rationale behind them:

Names Emphasizing Speed and Performance

QuickCache: Simple, direct, and highlights the core idea of fast caching.
BlitzDB: Evokes the image of lightning speed and power.
AccelStore: Focuses on the acceleration the product can provide in data retrieval.
ViperCache: Suggests fast and agile data access.
TurboStore: Implies performance enhancement and a boost to applications.

Names Referencing Core Functionality

CachePro: Emphasizes a professional-grade caching solution.
SwiftMem: Indicates rapid in-memory data operations.
DataSurge: Suggests a powerful flow of data, especially for high-volume scenarios.
SnapStore: Highlights fast read/write operations for a key-value store.

Names with a Playful Twist

KwikDB: Fun and memorable, while still suggesting speed.
ZippyCache: Implies a light, fast, and efficient solution.
FlashStore: Associations with fast storage and retrieval.

More Abstract but Evocative Names

Surge: Evokes the idea of a powerful, fast increase in activity (like data flow).
Nimbus: A reference to clouds, suggesting a lightweight, distributed nature.
Pulse: Suggests a heartbeat-like rhythm of central data operations.

Important Considerations:

Memorability: Choose something that's easy to remember and pronounce.
Originality: Double-check that your top choices aren't already trademarked.
Domain Availability: Ensure you can secure a relevant domain name.

Let me know if you want a more tailored list or have specific themes in mind!

from valkey.

Bredis and have it be stacked toast 🍞

from valkey.

Keyvi
kivi

Or some similar spelling. I recently went to New Zealand, if you haven't seen kiwi birds they are so adorable!

from valkey.

SalvatoreDB antirezDB

from valkey.

Redis
=>
Sider

from valkey.

It's a bit strong, but I do agree that the underlying issue that resulted in this mess would have avoided if Redis had distributed copyright with a copyleft license. I think it's worth considering whether the community here would like to merge with the sprouting Redict community and follow with that, since it's set up and has built out community engagement and governance.

from valkey.

OpenDis

from valkey.

Radish

• They taste nice
• Good opportunities for the logo
• Slight rhyme with Redis
• Got nothing more beyond that

from valkey.

Air (Air isn't Redis). But that would be only in the lore of the name, not in the marketing of the project).

Air evokes ideas of freedom, and public goods.

The general rule of law is, that the noblest of human productions — knowledge, truths ascertained, conceptions and ideas — become, after voluntary communication to others, free as the air to common use.

Judge Louis Brandeis, SCOTUS Justice in Dissent, International News Service v. Associated Press (1918).

See also writings of Yochai Benkler with titles like "Free as the Air to Common Use: First Amendment Constraints on the Enclosure of the Public Domain"

from valkey.

OpenStruct

from valkey.

Dass (DAta Structure Server).

And when you get it as a service, it's DassaaS

from valkey.

I'll give you one really good reason: it fixes the damn problem that brought us all here in the first place.

from valkey.

freedis.

from valkey.

Redis => Sider

@madolson ;)

from valkey.

While it's nice to see so many good suggestions we should do our best to deviate from the name "Redis" to avoid any potential trademark infringements.

from valkey.

KV Wentworth - Fast Cache Now!

from valkey.

Personally, I second OpenKV from @hpatro.

It rhymes well with other open-source projects such as OpenTofu and OpenSearch. If our goal is to move away from naming conventions similar "Redis", this would be our best option.

from valkey.

An alternative name that connects to its heritage would be RossoDB.
Italian roots and red as the fastest sports car.

(but I also think the suggested OpenKiwi is very likeable)

from valkey.

Replace the V with a W?

Perhaps add 'db' suffix for database (kiwidb)? Or just an 's' for server (kiwis)?

from valkey.

fledis - For those of us who have "fled" open source Redis after Garantia Data took it

from valkey.

MemoryDB

Redis has more functionality than a simple key-value store, and this name is generic and quick to understand universally.

This conflicts with the existing MemoryDB service which may be an issue.

from valkey.

EmberDB

from valkey.

Maybe a play on musical notes? "Redis" is "DD#": "re" is Latin for "D", "dis" is German for "D#". There are a lot of names that could be thought up based on this theme.

from valkey.

OpenRedis?

It worked pretty for OpenSearch, with a name that clearly states the goal of the project: being the [true] open-source version of Elasticsearch. Also, I agree with others about the K/V semantics. Redis is far more than just a key-value store. It's vast set of supported data structures is what makes it so flexible and powerful.

from valkey.

Redict was a good name. We'll have to relate to them (the new LGPL fork) since they'll be part of the landscape, at least initially. Independent clients from now on might more officially target all of KeyDB, Redict and others. The name is good, since it's not r*dis, yet similar enough so people understand what it is.

• OpenKVDB
• Addict, Verdict, Predict, Contradict (with or without DB suffix)
• Eddie's
• Prejudis
• Sider, if it's an acronym (like storage information distribution enhanced register, or whatever, ask chatgpt) or Siderton (not redis, backwards)

from valkey.

OpenRedis?

Anything with Redis in it is not going to fly due to obvious trademark reasons.

It worked pretty for OpenSearch, with a name that clearly states the goal of the project: being the [true] open-source version of Elasticsearch.

But "OpenSearch" does not contain "Elasticsearch", only "search", which is a descriptive term and not trademarkable in this context.

from valkey.

Redis came from Remote Dictionary Server... so maybe Open Dictionary Server -> Odis

Why not Open Remote Dictionary Server ->Oredis

if it can not contain redis, we can call it. Ordis

from valkey.

Medis (short for Maddy's)

from valkey.

Rapidus

from valkey.

While it's nice to see so many good suggestions we should do our best to deviate from the name "Redis" to avoid any potential trademark infringements.

Yeah, I've been silently ignoring them. It's good to say this explicitly, we don't want anything that can be confused with Redis.

from valkey.

I like OpenKV (also OpenKVS)

from valkey.

Why not use KV in Kiwi, Kivi? Or KeeVee?

from valkey.

I like OpenAir. Not a big fan of Free because that is copyleft, free software foundation :) I think we should stick to nomenclature that fits well with BSD licensing.

Sir, FreeBSD is right there.

from valkey.

KV Wentworth - Fast Cache Now!

Underrated comment 😆

from valkey.

How about honoring antirez in the new name? CataniaDB (the town where he lives)

from valkey.

Voltair like high voltage and fast

from valkey.

Since we're in the era of "is there an emoji for the name", here's some emoji suggestions for FreeAir🍃

FreeAir🍃
FreeAir🌬
FreeAir💨

I kind like the first one. “I am a leaf on the wind. Watch how I soar.”

from valkey.

@madolson:

@Conan-Kudo The contributors have been side channeling and really like the idea of using Kiwi, something like OpenKiwi. I want to respect your wishes in avoiding using "kiwi" though, so wondering if there is anything that would make you happy about how "different" it has to be.

"KeeVee" would work and be sufficiently disambiguated while still sounding similar enough for those who like the sound.

from valkey.

Perhaps add 'db' suffix for database (kiwidb)? Or just an 's' for server (kiwis)?

That would make it sound like the main focus is the DB, which has a similar reasoning as of why @madolson wants to stay away from KV. I'd assume something neutral that leaves room to expand and interpretation would be more suitable.
I like Kiwis though or OpenKiwis, the latter having a fun abbreviation aswell (OK), which would fit the response messages.

from valkey.

If you're absolutely dead set on "kiwi", then OpenKiwis is fine, with the commands being openkiwis-* to be fully disambiguated from the kiwi command name by the kiwi image builder tool.

from valkey.

kiwis looks good

from valkey.

PrismDB
PrismKV

RealmDB
RealmKV

These are my suggestions :D

from valkey.

Keyvi kivi

Or some similar spelling. I recently went to New Zealand, if you haven't seen kiwi birds they are so adorable!

+1. I was suggesting kiwi earlier since it sounds close to KV (Key-Value).

from valkey.

OrcaKV
VoltKV (VoltDB already exists)
BrisKV
SwiftKV (I know not this one)
SleeKV

from valkey.

ReVo (redis evolution)

from valkey.

ReOpen but may have trademark conflicts

from valkey.

Hear me out: "Desir"
And if you ever do a serverless version: "Desirless"

from valkey.

kv

from valkey.

Koshis - Kosh stands for storehouse in Sanskrit.

from valkey.

Most of these are good names: Odis is a particular favorite of mine

unfortunately, odis.io is taken and odis user is taken in github. Before suggesting a name I suggest to check if it is available at least on github. I am guessing that's what @madolson did wiith openkvs: https://github.com/openkvs/

from valkey.

fastore?
though there are bunch of old github projects with this name :( even fastoredis 🤷‍♂️

from valkey.

Yeah, TARDIS (Time And Relative Dimension In Space) is bigger on the inside than on the outside. :D And it'd be funny when people search for docs and find Dr. Who fan sites instead...

(When I suggested retardis above, it was also a reference to TARDIS, though i didn't explain that.)

from valkey.

SpeedyCache, as it's known for its high speed and efficiency as an in-memory caching system.

from valkey.

RediStore, as it sounds similar to Redis and emphasizes its role as a data storage system.
Or maybe RediCache, as it is a kv cache store more precisely.

from valkey.

inmdb = in memory database
inmkv

from valkey.

openkvs / radish are good.

Also building on "sider" -- "ciderkv" or "cider" could be fun. Has a phoenetic conflict with CIDR, though... naming is hard.

from valkey.

I think one of the primary distinctions with this software is the data structures. How about names around that?

structuresd (structures daemon, it's not an init process, but not a d suffix things are these days)
keystructures (very descriptive. it's literally the data model: keys that point to structures)
structserv(a server for structures)

Personally, I'd love a name that doesn't call back but moves forward and describes what the software does at the same time. ('Remote Dictionary Server' didn't do a good job at the latter, imho. It was often used locally and it was about way more than just a dictionary)

from valkey.

I like Radish but the namespace is not available here on GH or NPM so maybe RadishKV is a good option.

from valkey.

I like Radish but the namespace is not available here on GH or NPM so maybe RadishKV is a good option.

Radish is too close to Redis unfortunately :(

from valkey.

@Conan-Kudo The contributors have been side channeling and really like the idea of using Kiwi, something like OpenKiwi. I want to respect your wishes in avoiding using "kiwi" though, so wondering if there is anything that would make you happy about how "different" it has to be.

from valkey.

Working off the "Air" theme, you could do "FreeAir" or "LibreAir".

Personally I like "FreeAir" the most because it echos the "Free as the air to common use" quote.

[edit] removed my suggestion of "OpenAir".

from valkey.

Working off the "Air" theme, you could do "FreeAir", "LibreAir" or "OpenAir".

Personally I like "FreeAir" the most because it echos the "Free as the air to common use" quote.

I like OpenAir. Not a big fan of Free because that is copyleft, free software foundation :) I think we should stick to nomenclature that fits well with BSD licensing.

from valkey.

I imagine that it would be good if you can Google it without competing with existing software (Hades would have been cool though) and something that is easy, intuitive, and not a bastardization of another word to spell (looking at you Visilibity)

from valkey.

Posthaste

from valkey.

In order to honor our place holder abbreviation, phkv, PheonixKV.

from valkey.

Phoenix, like rising from the ashes. Not bad.

from valkey.

Radish is too close to Redis unfortunately :(

Terraform became OpenTofu, so Redis becomes OpenRadish? 😉

OpenRadish sounds like a skin disease.

from valkey.

“The instruction we find in books is like fire. We fetch it from our neighbours, kindle it at home, communicate it to others, and it becomes the property of all.”
—Voltaire

(if you Know, you Know).

from valkey.

OpenReydis

from valkey.

I like the idea of empty names, where the name is not bound to context of the offering but is rather a reflection of how owners see it. For example - Amazon

As such, I'd propose 'halo' (as opposed to the horns we don't want this fork to be)

from valkey.

@Conan-Kudo

@madolson:

@Conan-Kudo The contributors have been side channeling and really like the idea of using Kiwi, something like OpenKiwi. I want to respect your wishes in avoiding using "kiwi" though, so wondering if there is anything that would make you happy about how "different" it has to be.

"KeeVee" would work and be sufficiently disambiguated while still sounding similar enough for those who like the sound.

Yeah, the problem is we want to stay away from KV. The idea was that we want to move away from the key/value association, and we thought kiwi was a playful way to do that. It sounds like KV, but isn't quite that. It's more abstract.

from valkey.

Replace the V with a W?

from valkey.

@Conan-Kudo Your opinion is the one I care about, thought about OpenKiwis? (No offense to other, they originally brought it up)

EDIT: We could also maybe call the project OpenKiwis, but call the actual server Kiwi-server. AFAIK, kiwi is an image builder, so kiwi-server should make it clear it's something else. kiwi-cli, kiwi-benchmark, etc.

from valkey.

If you're absolutely dead set on "kiwi", then OpenKiwis is fine, with the commands being openkiwis-* to be fully disambiguated from the kiwi command name by the kiwi image builder tool.

We're not deadset, but we don't have a lot of time to get everyone together to discuss because of time zones, and we're trying to pick a name sooner.

from valkey.