3 ms·
It rebranded in 2015. It used to describe itself as a cache (earlier revisions also declare themselves to be a memory store) https://web.archive.org/web/2015030
by SillyUsername 3y ago
It rebranded in 2015. It used to describe itself as a cache (earlier revisions also declare themselves to be a memory store)
https://web.archive.org/web/20150304014343/http://redis.io/ https://web.archive.org/web/20150304014343/http://redis.io/
I consider it to be cache first, "db" second, with true definition of db first being something that can execute SQL or SQL like statements (such as Cassandra's CQL).
It's the same reason I don't call Cassandra a cache, although it can achieve the same result.
- JohnBooty 3y agotrue definition of db first being something that can execute SQL or SQL like statements Pedantic note: the term "database" existed long before the relational model or SQL existed. Many of the dominant databases of the 80s and 90s (dBase, etc) would not fit your invented definition. Additionally, a lot of "toy" databases like Access can execute SQL statements, so the ability to execute SQL statements isn't necessarily a great way to tell what's a "real" database. In practical terms, I do agree with you -- if somebody in 2023 is referring to "the database" in their app they had darn well better be talking about something robust and ACID-compliant like Postgres or whatever.
- viralpraxis 3y agoYour definition does not make any sense. Imagine defining « prime numbers » as {2,3,5} set