HN Explorer

Ask HN: The continue of that Digg and Cassandra story?

1 points by c00p3r ↗ HN
Recently I've visited http://cassandra.apache.org/ and the front page remains the same - Proven! Digg uses it! and so on. No mention of an epic failure, of course.

So what is new? Did they manage to figure out why it cannot work under a heavy load? It that Cassandra's or general Java issues?

3 comments

[ 3.4 ms ] story [ 15.5 ms ] thread
DiabloD3
From what I've seen of Cassandra, it was started by people who confused MySQL with the general state of SQL implementations.

In fact, many of these database implementations produced by NoSQL movement aren't anti-SQL, they're anti-MySQL; and the authors don't realize it as they've used PostgreSQL or Oracle in depth.

I seriously doubt this is a Java issue, and it might not be a Cassandra issue either... it could very well just be a an issue with how Digg is coded.

hga
As I remember many said that Digg made substantial modifications to Cassandra, which further muddies the water depending on which levels of it they modified.

However, the key thing to me was that they were fixing break the world bugs a few days before the release, which tells us their engineering and release management was horribly broken. I don't see how we can blame Java, Cassandra or their modifications to the latter when they ignored clear signals their new total rewrite wasn't ready for prime time.

drevell
Reddit, who is eating Digg's lunch, relies heavily on Cassandra.

This is a Digg Fail and not a Cassandra Fail.