RedPanda seems to be a better starting point to be honest - a lot of the market share for Cassandra doesn't actually need the extra tps of Scylla. Some customers do, but many many many do not.
793 karma · joined December 10, 2013
RedPanda seems to be a better starting point to be honest - a lot of the market share for Cassandra doesn't actually need the extra tps of Scylla. Some customers do, but many many many do not.
A pyramid scheme that has electricity consumption of bitcoin? Strictly a net loss for the world.
This is the hard part of software.
The cardinal rule of database development:
http://www.dbms2.com/2013/03/18/dbms-development-marklogic-h...
Xbox was always consumer and is massive. A huge chunk of the Windows line was always about consumers. The office line straddled both. Hotmail was consumer first.
(Designed for correctness testing at petabyte scale)
That doesn't say the job is ONLY converting code. It says that code was converted, and new code will be in Rust.
Given its success, lack of pricing pressure makes sense - until users go away, there’s little reason to decrease margins.
It’s not a startup-driven product that is worried about AWS as a competitor.
> Considering the kind of resources Apache Cassandra requires to run
Makes no sense. There is plenty of talent at AWS to run Cassandra proper on AWS for less money than they're currently charging for Dynamo. This was true before this announcement - it's how people like Instaclustr stay in business (containerized cassandra as a service on EC2).
A lot of that is getting better over time. A non-trivial percentage of contributions are coming from companies that are only looking to improve their operational story, not adding new features.
Most of the talks at NGCC (Next generation cassandra conference) focused on operational improvements - it's something we care a lot about (myself especially).
- Feature sets aren't the same yet
- History / maturity
- License
- Actual savings dont tend to match proposed savings
- Development isn't driven by a startup that AWS can kill with an announcement like this.
Assigning blame is done after the fact to make up for a mistake.
Just avoid the mistake.
This is the type of nonsense I expect from HN. Well done.
Those "specialized tools" make email viable. Without it, everyone would be spoofing everything and you wouldn't use email anymore.
Then EVERYONE stopped because it's awful. Modern ISPs don't like SMTP floating around, (DKIM, DMARC, SPF) are a pain to maintain over time, exploits will happen, and your free off-the-shelf virus and spam filters suck compared to the big companies seeing billions of messages per day.
Employee 3
Hi, my name is [redacted]. (audience applause)
Marcelo Claure
Well first you’ve got to tell me why the people like you so much? (audience laughs)
Employee 3
Because I asked a question at the last All-Hands meeting.
Marcelo Claure
Okay.
Employee 3
I’m with the Development Finance Group, I do data analytics and reporting and today’s my one-month anniversary at WeWork. (applause)
Marcelo Claure
You’re very popular for one month.
Not asking anyone to dox employee 3, but I’d really love to know what the backstory there is.In Cassandra, we use MTs during active anti-entropy repair, where we have N replicas of some data and want to make sure they’re in sync
The repair command will repair a range of data - in real terms, it’s repairing all keys between two tokens, where the token is the murmur3 hash of the key. The whole cluster covers 2^64, but a typical repair will repair perhaps 2^40 or smaller.
When you’re repairing 2^40 keys, you don’t want to compare each of them one by one - if they match, you’re sending a ton of data across the network for no reason. Instead, if each replica builds a needle tree representing the data for that range, you can not only tell quickly if they’re in sync (comparing the roots), but you can descend to identify the minimal set of data to stream between replicas.
The Cassandra implementation isn’t a textbook implementation of the concept, but it’s easy to think about.
Also, cql is now implemented by like 5-6 nosql databases and is becoming the implicit standard (Cassandra, cosmosdb, datastax, yugabyte, etc).