5 ms·
I would imagine that this project was a Not Invented Here sort of thing when Redis was presented as an option. Total conjecture on my part.
by jensenbox 3y ago
I would imagine that this project was a Not Invented Here sort of thing when Redis was presented as an option.
Total conjecture on my part.
- parhamn 3y agoAh yes, redis, the first distributed KV store that wasn't NIH.
- bradhe 3y agoRight and don’t you understand that Redis has the availability guarantees, scaling constraints, and memory architecture for all use cases?! Why would you ever need a different KV store when you have Redis!
- PlutoIsAPlanet 3y ago> Why would you ever need a different KV store when you have Redis! If you want to have tier based storage, where you trade off latency for increased data size, meaning disk space is your limit and not your RAM.
- bradhe 3y agoI was being sarcastic.
- pgt 3y agoEverything in Redis has to fit in RAM.
- bradhe 3y agoMy statement was sarcastic.
- avinassh 3y agoIs Redis safe? I make a SET request and before the data is written to disk, if Redis crashes, my data is gone for good, right? edit: Redis supports fsync at every query in AOF mode https://redis.io/docs/management/persistence/#ok-so-what-should-i-use https://redis.io/docs/management/persistence/#ok-so-what-sho...
- bradhe 3y agoI was being sarcastic.
- astrea 3y agoThat's how I feel about all of these such things developed by big companies.
- threeseed 3y agoIf you're smarter than the hundreds of engineers designing and building the distributed systems powering the world's largest applications then well done. Personally, whenever I see a system like this I try to look for why they didn't go with an existing solution. And in 99% of cases either an existing solution never existed or they had a unique requirement that necessitated building something from scratch.
- astrea 3y agoYou're assuming a level of engineering/scientific "purity" that doesn't really exist within orgs to the idealistic extent that we would like to imagine. I'm not saying that I'm smarter than every FAANG engineer, but having met quite a few and worked in large orgs myself, it's easy to say some of these tools come from pride/arrogance/a need to have your name on something/a fundamental misunderstanding of existing tooling. Not necessarily because they're unraveling parts of the universe yet unexplored and need a bespoke weapon to tackle new issues.
- JustLurking2022 3y agoHonestly, I work at a FAANG and, sadly, the answer is often a combination of people paying absolutely zero attention to tech that's NIH (e.g. SWEs working on DBs who have never used Postgres) and the fact that no one gets promoted for implementing a solution using 3rd party software. The system is setup such that you need to show you've developed something of sufficient complexity, and using OSS just doesn't look good in that context.
- threeseed 3y ago> DBs who have never used Postgres PostgreSQL is great for single instances but is poor when it comes to high availability and horizontal scalability. Be curious what use cases where engineers are writing their own database but it is single instance.
- vichle 3y agoRedis was not a distributed system a decade ago.
- wg0 3y agoThis is based on RocksDB which is "sorted key value" store like LevelDB (HBase, Hypertable etc.) and keep sorting and merging keys while flushing to disk at certain point. Redis in comparison is a different thing if I'm not wrong.
- JustLurking2022 3y agoIt's a valid point - RocksDB can be thought of as the internal backend implementation of the DB. It's the front end API that matters as to whether Redis could fulfill the same purpose.
- bushbaba 3y agoWhy do you need junk then if rocksdb exists?
- antonvs 3y agoJuno is a disk-based store - a closer comparison would be to Mongo. And back when Juno development started, Mongo would not have seemed like a very good option (if it even is today.) Also, Redis was not originally distributed.
- orra 3y ago> Juno is a disk-based store The question is definitely interesting. And to be fair, Juno was originally in memory.
- threeseed 3y agoMongoDB is a document database not a key-value store. That distinction is massively important when you're talking about distributed systems as key-value has far less edge cases to consider. Also its architecture is quite different as it doesn't have the concept of proxies. Basically in the realm of databases the two are nothing alike.
- redwood 3y agoYou can think of key / value as a subset of document namely one with a single index
- ilyt 3y agoKV database is just fun enough project to be NIHed many many times