Jonathan Ellis
spyced.blogspot.com · Personal blog · on HN since 2007
Jonathan Ellis, a developer and Apache Cassandra project leader, writes about distributed databases, Cassandra releases, and data structures like bloom filters.
What HN saysHN commenters link his bloom filter write-up as a reference for hashing and Cassandra's internals, and his Cassandra posts for project plans and database comparisons.
23HN people shared it
8linked it in comments
19stories submitted
274story points
2 years agolast shared
2007people per year2026
Most-shared posts
- 1All you ever wanted to know about writing bloom filters3 people · 1 points · first shared 2009 · discussion on HN
- 2Cassandra in action2 people · 57 points · first shared 2010 · 5 comments on HN
- 3Cassandra 0.5.0 released2 people · 27 points · first shared 2010 · 8 comments on HN
- 4Cassandra: Fact vs fiction1 people · 57 points · first shared 2010 · 23 comments on HN
- 5Why CouchDB doesn't scale1 people · 50 points · first shared 2009 · 30 comments on HN
- 6Apache Cassandra in 2010: Code, Community, and Controversy1 people · 35 points · first shared 2011 · 2 comments on HN
- 7Why I like Cassandra (distributed database)1 people · 18 points · first shared 2009 · 4 comments on HN
- 8Why you won't be building your killer app on a distributed hash table1 people · 8 points · first shared 2009 · 2 comments on HN
- 9A Week of Windows Subsystem for Linux1 people · 3 points · first shared 2024 · discussion on HN
- 10Python IDE update1 people · 3 points · first shared 2008 · discussion on HN
- 11Speaking to a technical conference1 people · 3 points · first shared 2012 · discussion on HN
- 12Jonathan Ellis on his new Cassandra Company1 people · 2 points · first shared 2010 · discussion on HN
- 13The Missing Piece in AI Coding: Automated Context Discovery1 people · 2 points · first shared 2024 · discussion on HN
- 14Cassandra:a better analysis1 people · 2 points · first shared 2009 · discussion on HN
- 15The business case for Google App Engine1 people · 2 points · first shared 2008 · discussion on HN
What HN people wrote when they linked it
jbellis · 2014-02-01
He missed the best way to generate hashes. Most people do: http://spyced.blogspot.com/2009/01/all-you-ever-wanted-to-know-about.h…
pchivers · 2008-06-03
Spyced (Jonathan Ellis): http://spyced.blogspot.com/
jamie · 2010-04-08
This is in the Summer Of Code roadmap:
http://spyced.blogspot.com/2010/03/cassandra-in-google-summer-of-code-…
skorgu · 2010-03-26
Cassandra is hugely biased towards making writes fast [1] and there's no indication in either Digg article that they (somehow) changed that fact in their deployment by tuning. Digg loads the complexity during the write by denormalizing but that load is on the application server not the data store.
[1] http://spyced.blogspot.com/2010/01/cassandra-05.html
kiwidrew · 2009-05-20
related: cassandra's use of bloom filters
http://spyced.blogspot.com/2009/01/all-you-ever-wanted-to-know-about.h…
and also related: murmurhash, a hash which is well-suited for bloom filters and that is much faster than SHA-1
http://murmurhash.googlepages.com/
inklesspen · 2008-04-28
You did in fact say web2py won:
"web2py is the only framework that participated to the www.flourishconf.com rumble (develop a web app in 24 hours) and won because all the other frameworks chickened out."
http://spyced.blogspot.com/2008/04/m-half-baked-thoughts-on-python-web…
jqueryin · 2010-04-06
This happens to be an oldie but a goody. On the same topic, I might as well spread the wealth of links I've amassed for learning and understanding Cassandra:
Up and Running With Cassandra
http://blog.evanweaver.com/articles/2009/07/06/up-and-running-with-cas…
Building A Small Cassandra Cluster
http://posulliv.com/?p=149
Cassandra PHP CRUD Class (Pandra)
http://github.com/mjpearson/Pandra
Getting Started - CassandraWiki
http://wiki.apache.org/cassandra/GettingStarted
Cassandra In Action
http://spyced.blogspot.com/2010/03/cassandra-in-action.html
yaaang · 2011-06-23
First off - whatever you're doing, you'll probably be fine using either.
That said, I'm generally more frustrated when using MySQL than when using PG. Here's a sample of the problems I've encountered from using both MySQL and PG. I haven't updated my list in a while now - please feel free to correct me on things - but hopefully it's a little more illustrative than that Wikipedia feature matrix, and a little more specific to MySQL vs. PG. (This list is a cleaned-up selection from my notes wiki at http://yz.mit.edu/notes/Hackery.)
No referential integrity.
No constraints (CHECK).
No sort merge join, let alone hash-join. http://www.dbms2.com/2008/07/10/how-is-mysqls-join-performance-these-d… http://www.mysqlperformanceblog.com/2006/06/09/why-mysql-could-be-slow…
Generally poor at analytical workloads, since it's designed for transactional workloads.
Can't reopen TEMP table - WTF? (Still not fixed!) http://bugs.mysql.com/bug.php?id=10327
Multiple storage engines has always restricted progress: http://www.mysqlperformanceblog.com/2010/05/08/the-doom-of-multiple-st… (PG also supported multiple storage engines in 80s, then concentrated on one)
No WITH clause: http://stackoverflow.com/questions/324935/mysql-with-clause
Crappy errors: “Incorrect key file for table ‘stock’; try to repair it” on “alter table stock add constraint pk_stock primary key (s_w_id, s_i_id);” where stock is in InnoDB (which has no “repair table”) means I have no…