jbellis

46 ms·

601.
by jbellis 15y ago
Sounds like that's addressed by storing pieces of data from many sources in the non-local part of space monkey storage: even if each source only has a 256K uplink, multiply that by 100 or 1000 and you're in pretty good shape.
602.
by jbellis 15y ago
Upvoted, but I skimmed 5.1 and missed the "shown not to work" part. Can you be more specific?
603.
by jbellis 15y ago
From the same author, http://oscarbonilla.com/2009/05/the-monty-hall-problem/
604.
by jbellis 15y ago
And an explanation of the PBS paper as applied to Cassandra: http://www.datastax.com/dev/blog/your-ideal-performance-cons...
605.
by jbellis 15y ago
Curious what you found so hard about setting up Cassandra. Counterpoint: http://www.screenr.com/5G6
606.
by jbellis 15y ago
And yet, many iOS apps end up using screen space on a Back button. And I find myself missing it on those that don't.
607.
by jbellis 15y ago
Personally, I tried to share the original NYT article, but it was behind a registration-wall so I shared the Forbes one instead.
608.
by jbellis 15y ago
There's less to write about there... One of the first Cassandra decisions was dropping vector clocks, reasoning that vector clocks weren't worth the additional complexity for 99% of uses (once you move from key/value to rows + columns). Dy
609.
by jbellis 15y ago
I'm still struck by what a strong endorsement DynamoDB is of the design decisions we've been making in Cassandra over the last couple years. Composite keys, distributed counters, ... More details: http://www.datastax.com/dev/blog/amazon-d
610.
by jbellis 15y ago
Consistency and durability are two different things.
611.
by jbellis 15y ago
"There are only two hard problems in Computer Science: cache invalidation and naming things."
612.
by jbellis 15y ago
Be careful to compare apples to apples. Sure, the memory-only crowd (e.g, redis) will post higher numbers, but Cassandra is the performance leader for scalable, larger-than-memory datasets. See http://www.cubrid.org/blog/dev-platform/nos
613.
by jbellis 15y ago
See also: "Growing a language." http://video.google.com/videoplay?docid=-8860158196198824415 / http://cs.au.dk/~hosc/local/HOSC-12-3-pp221-236.pdf
614.
by jbellis 15y ago
It's basically the same design (both are good at indexing low-cardinality data, and poor for high-), except that Cassandra allows non-index predicates to also be filtered server-side during an index scan: http://www.datastax.com/dev/blog/w
615.
by jbellis 15y ago
I posted a comparison to Cassandra here: http://news.ycombinator.com/item?id=3480480
616.
Amazon DynamoDB vs Cassandra(datastax.com)
22 points by jbellis 15y ago|6 comments
617.
by jbellis 15y ago
I've drained my Evo using Maps while plugged in to the car adapter, as well. Frustrating.
618.
by jbellis 15y ago
My comment from TFA. Context: Paul Querna correctly pointed out that Cassandra has had Hadoop integration since 0.6, and the author replied that Cassandra was complicated. If your objection to Cassandra is "it's complicated," you have no b
619.
by jbellis 15y ago
I was confused because I didn't see any "exactly how they did it" in the linked article. Better link: http://blog.bufferapp.com/the-17-awesome-investors-in-our-40...
620.
by jbellis 15y ago
Schemaless doesn't necessarily mean "document-oriented." Sparse-column / ColumnFamily databases like Cassandra are a lot closer to "schemaless" than they are to "traditional rdbms schema."
621.
by jbellis 15y ago
I feel this guy's pain every time I have to wait half a second for a dialog to "scroll" into place on OS X instead of just appearing, damn it.
622.
by jbellis 15y ago
Many of these are elaborated on in the more recent (1999) "The Practice of Programming." Excellent book. http://www.amazon.com/Practice-Programming-Brian-W-Kernighan...
623.
by jbellis 15y ago
Your information is out of date. http://www.azulsystems.com/blog/cliff/2009-09-06-java-vs-c-p...
624.
by jbellis 15y ago
"If someone asks me for an honest opinion of them or their work, in private, I feel morally compelled to be as honest as I can with them." I can vouch for that. Around a year ago I asked him for feedback on Cassandra and his response was b
625.
by jbellis 15y ago
When I'm learning about a new architecture, I like to take the position of, "let's assume the authors aren't idiots. If they're not, why would they have designed things this way?" With that in mind, let me pose this question to you. Is usi
626.
by jbellis 15y ago
That boils down to Chip's opinion that master/slave is the One True Way to do replication, despite its many demonstrated disadvantages. I see your Chip Salzenberg and raise you a Werner Vogels: http://www.allthingsdistributed.com/2008/12/
627.
by jbellis 15y ago
IIRC Ferriss arrived at his "four hour" week exactly by not counting work-related activities he enjoyed, as work.
628.
by jbellis 15y ago
NeXT was not cheaper; Gassee wanted 275M for BeOS, and they bought NeXT for 429.
629.
by jbellis 15y ago
1) The explanation of Cassandra isn't quite correct. See http://www.datastax.com/docs/1.0/cluster_architecture/replic... for details. 2) Cassandra read performance is on par with writes now: http://www.datastax.com/dev/blog/whats-new-in
630.
by jbellis 15y ago
Their claims reminded me of Jim Starkey's history with the CAP theorem: http://pl.atyp.us/wordpress/index.php/2010/03/cap-and-leases...

More ›