Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Learning Apache Cassandra

You're reading from   Learning Apache Cassandra Managing fault-tolerant, scalable data with high performance

Arrow left icon
Product type Paperback
Published in Apr 2017
Publisher
ISBN-13 9781787127296
Length 360 pages
Edition 2nd Edition
Languages
Concepts
Arrow right icon
Author (1):
Arrow left icon
 Yarabarla Yarabarla
Author Profile Icon Yarabarla
Yarabarla
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

1. Getting Up and Running with Cassandra FREE CHAPTER 2. The First Table 3. Organizing Related Data 4. Beyond Key-Value Lookup 5. Establishing Relationships 6. Denormalizing Data for Maximum Performance 7. Expanding Your Data Model 8. Collections, Tuples, and User-Defined Types 9. Aggregating Time-Series Data 10. How Cassandra Distributes Data 11. Cassandra Multi-Node Cluster 12. Application Development Using the Java Driver 13. Peeking under the Hood 14. Authentication and Authorization

Cassandra data modelling


Cassandra data modeling is the process of designing tables. This could involve drawing up an entity-relationship diagram, designing tables based on queries, and finally, making optimizations based on the features supported by Cassandra. Ideally, the data model can be split into three levels of abstraction:

  • Conceptual data model: A conceptual data model represents a high level view of the data. It is technology agnostic and not specific to Cassandra or any other database system. The purpose of creating a conceptual data model is to understand the data. We get a clear idea of the entities involved and the relationships between different entities. For our case, we will be using the entity relationship model as the conceptual data model.
  • Logical data model: A logical data model will act as a bridge between the business case and the final table design. We will use the conceptual model and apply query-driven design rules to get a logical data model.
  • Physical data model: A...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime
Visually different images