bloodredsun : The long and short of it is that Cassandra is a fantastic system for write heavy situations. What it is not good at are read heavy situations where deterministic low latency is required, which is pretty much what the pinterest guys were dealing with.
@ viktorklang : "The e-mail message could not be delivered because the user's mailfolder is full." <-- EMAIL HAS BACKPRESSURE OMG
Interesting Behind the Scenes: . … Neighborhoods
…he ported a relational database to threedata stores: , Cassandra and .
- Greg Unrein demonstrates how to make Openmix decisions with data.
- explains how to use 3.2 with 1.9.3 on .
- two-year plan for .shares their
- shares four things you should consider when selecting a cloud provider.
…Amazon has built all of the above on top of the basic Dynamo ingredients, Cassandra living proof that it's possible. But if Amazon did reuse a lot of the existing Dynamo code base, they hid it really well. All the evidence points to at least heavy usage of a sorted storage system under the covers, which works very well with SSDs, as they make sequential writes and reads nice and fast.
No matter what it is, Amazon has done something pretty great here. They hide most of the complexity …
You're in good hands with HighScalability :
Netflix - Cassandra, . , 288 instances, 3.3 million writes per second
@ bretlowery : "A #DBA walks into a # bar, but turns and leaves because he couldn't find a table."
@ eden : Ori Lahav: "When planning scalability, think x100, design x5 and deploy x1.5 of current traffic"
…went to town. The result was a combination of Google Protocol Buffers, node.js, and Cassandra. Elegant, scalable, and totally unmaintainable.
"How many devices do we expect to have?"
"Well, we hope to sell 500 in 12 months."
"How often will they need to report in?"
Are future updates included?
Yes, as content gets added, typos get fixed, and new databases pop up, I'll send updates to everyone buying the book. The updates are free. Consider buying the book a subscription for more chapters on other databases.
Are you extending the book with more databases over time?
Yes, I have an insatiable thirst to …
They use Cassandra in multiple regions, and it works well for them.
EBS snapshots can't cross regions.
There is no one size fits all solution.
The most common approaches they see involve multi-AZ configurations with a solid DR plan.
This talk summarizes the history of Amazon retail from 1995 to 2011. I think the switch to AWS was in 2011.
As performance was critical, the solutions that could in any way impact the efficiency of the application were dismissed. Thus, we crossed out Cassandra, since it's written in Java and could require substantial memory resources and JVM installation. The application was created utilizing Ruby on Rails, therefore the key-value solution to be chosen …
…leaks, no restarts). Internally, we use it to interface with, , Cassandra, as well as many other local and remote web-services. Goliath supports keep-alive, request pipelining, and can be used to build real-time, streaming 's - all features we use to optimize our infrastructure.
Which one will work best for the problem at hand? What if we could try them all really easily by just changing which place the data went to? What if we could try out more than one at once?
I sat down one weekend and started thinking about the app and realized what I just talked about above. Along the way, our data access changed from relational to key lookups. This made me think about a hash.
Hashes are so versatile, …