5 ms·
Aside nit-pick: I think is dangerous call anything "db" if is not safely stored with Acid. People not read docs neither know the consequences of words like "ev
by mamcx 4y ago
Aside nit-pick: I think is dangerous call anything "db" if is not safely stored with Acid.
People not read docs neither know the consequences of words like "eventual" or "in memory" and star using this kind of software as primary data stores, instead of caches/ephemeral ones...
- staticassertion 4y agoSo Cassandra isn't a database? I'd say "thing that manages data" is a database, which is to say, a lot of things are databases.
- cormacrelf 4y agoEverything is either a database or a compiler.
- vorpalhex 4y agoI think thats an issue with people who don't read/comprehend the docs.
- wutwutwutwut 4y agoHaha, what. If you run a database without reading the documentation then you're the dangerous part, not the ACID-compliance aspects. For _any_ database there will be important information only available in the documentation.
- mamcx 4y ago> If you run a database without reading the documentation then you're the dangerous part I think that covers almost all the whole dev population, for what I see in relation with RDBMS. Lucky us most RDBMs shield the mistakes in their usage, a lot. That is why I see is "dangerous" to call ephemeral/eventual stores as "db". Marketing/positioning have impacts...
- wutwutwutwut 4y agoAll databases are ephemeral if the person running it don't read the docs. Your comment is hence fully redundant, as opposed to the default single-node install of any DBMS.
- morelisp 4y agoAll of A, C, and I only make sense defined relative to a particular transaction vocabulary. Redis is perfectly ACID, as long as your transactions are those supported by Redis's commands. Conversely, plenty of DBs with programmable transactions (e.g. SQL) are considered work-a-day "ACID" enough, despite some massive gaps in their transactional model (no DDL in transactions, no nested transactions, atomic only when below a certain size, etc.)
- deleted 4y ago[deleted]
- romange 4y agoOk you got us. We chose dragonglydb and not dragonflystore just because the former sounds better on tongue :) Having said that we carefully choose to write everywhere in the docs thay we are in-memory store (and not the database). Btw, I reserve full rights to provide full durability guarantees for DF and to claim the database title in the future.
- vvern 4y agodragonflycache sounds reasonable.