miracle

"Follows the bigtable model, so it's more complicated than it needs to be. (300+kloc vs 50 for Cassandra; many more components). This means it's that much harder for me to troubleshoot. HBase is more bug-free than Cassandra but not so bug-free that troubleshooting would not be required."

I only had problems (data losses) when I was using HBase in production 3 months ago, but I'm certain that HBase will be mcuh more stable in a few months. And there comes that Cassandra developer and says that Cassandra even has more bugs. Lol. Now I'm pretty sure that I will never touch Cassandra as well.

Nice writeup. Should have mentioned hbase as well.

They should go to jail since they are making big money out of other people's copyrighted work.

And hopefully they will.

After processing large amounts of data, I was merging multiple lucene indexes and got random null pointer exceptions. Surprisingly when I was trying to run the offending code alone, everything worked fine. Took me a while to figure that one out. Turned out that it was a bug in the JIT Compiler of Java 1.6.

The most important thing is the team you are working with. Always try to get into a team where you are the most stupid team member.

No need to protocol ips anymore, the police simply needs to raid all the people paying for that service. :)

What about traffic?

2000000 * 40KB(Average compressed) / (10241024) 0.1 = 7.6 $. That's alone the cost to transfer it to your datacenter. I can'r reliably access the data on remote clients.

I guess the 2$ pricing tag is just marketing blah blha