Building high-performing Cassandra data models requires a query-based approach. However most of us were taught to build relational, normalized data models, which do not work well with Cassandra. Poor performing data models are often built with the idea of storing data efficiently, and then showered with secondary indexes to serve the required queries. Isn't it time that we learn how to build 21st century data models, without using 1970's techniques?
Aaron Ploetz - AccuLynx
Aaron is the Lead Database Engineer for AccuLynx, where he implemented Cassandra to scale part of their cloud-based business management system. He is active in the Cassandra tags on StackOverflow, has been working with Cassandra since version 0.8, and writes articles about Cassandra data modeling. Aaron holds a B.S. in Management/Computer Systems from the University of Wisconsin-Whitewater, a M.S. in Software Engineering and Database Technologies from Regis University, and was selected as a DataStax MVP for Apache Cassandra in 2014.
