Cassandra Sizing. Cassandra Data Modeling Best Practices, Part 1 — eBay Tech Blog. This is the first in a series of posts on Cassandra data modeling, implementation, operations, and related practices that guide our Cassandra utilization at eBay.
Some of these best practices we’ve learned from public forums, many are new to us, and a few still are arguable and could benefit from further experience. In this part, I’ll cover a few basic practices and walk through a detailed example. Even if you don’t know anything about Cassandra, you should be able to follow almost everything. A few words on Cassandra @ eBay We’ve been trying out Cassandra for more than a year.
Our Cassandra deployment is not huge, but it’s growing at a healthy pace. RedLaser, Hunch, and other eBay adjacencies are also trying out Cassandra for various purposes. I’m sure you have more questions at this point. The focus of this post is Cassandra data modeling best practices that we follow at eBay. Terms and Conventions The terms “Column Name” and “Column Key” are used interchangeably. Why? How? Notes: Summary. DataStax Cassandra 1.0 Documentation. For developers new to Cassandra and coming from a relational database background, the data model can be a bit confusing.
The following section provides a comparison of the two. The Cassandra data model is designed for distributed data on a very large scale. Although it is natural to want to compare the Cassandra data model to a relational database, they are really quite different. In a relational database, data is stored in tables and the tables comprising an application are typically related to each other. Data is usually normalized to reduce redundant entries, and tables are joined on common keys to satisfy a given query. For example, consider a simple application that allows users to create blog entries. In Cassandra, the keyspace is the container for your application data, similar to a database or schema in a relational database.
For example, using the blog application example, you might have a column family for user data and blog entries similar to the relational model. Intro — Hector - Java Client for Cassandra. The Apache Cassandra Project. GettingStarted. Cassandra documentation from DataStax DataStax's latest Cassandra documentation covers topics from installation to troubleshooting, including a Quick Start Guide.
Documentation for older releases is also available. Introduction This document aims to provide a few easy to follow steps to take the first-time user from installation, to running single node Cassandra, and overview to configure multinode cluster. Cassandra is meant to run on a cluster of nodes, but will run equally well on a single machine. Step 0: Prerequisites and Connecting to the Community Cassandra requires the most stable version of Java 7 you can deploy, preferably the Oracle/Sun JVM. The best way to ensure you always have up to date information on the project, releases, stability, bugs, and features is to subscribe to the users mailing list (subscription required) and participate in the #cassandra channel on IRC.
Step 1: Download Cassandra Download links for the latest stable release can always be found on the website. Cassandra.