Skip to main content

Book Review: Cassandra High Availability

Offtopic: My first book "High performance in-memory computing with Apache Ignite" has been released and available at http://leanpub.com/ignite.

This post is my review of the Packt Publishing book Cassandra High Availability by Robbie Strickland. As the main title suggest. The book has almost 186 pages covering 9 chapters and must read for Cassandra users.

Chapter 1: Cassandra's approach to High Availability
The initial chapter of Cassandra High Availability cover some architectural design such as Monolithic Architecture, Master slave Architecture and the Cassandra's approach to achieve high availability. Most of all modern software system requires a non functional requirements such as High availability. In this chapter author briefly describe why RDBMS is the single point of failure and is not suitable for horizontal scaling, also the drawback of the Master Slave architecture. In the next few section Author describe the Cassandra's architecture and it's approach to solve the problem with high availability, also introduce Cassandra's replication mechanism which make Cassandra DB more unique than other NoSQL DB.
Chapter 2: Data Distribution
This chapter introduce Cassandra's Data distribution strategy such as consistency hashing, tokens, vnodes and various practitioner. Author briefly describe Cassandra token arrangements such as manually assigned tokens and Vnodes, even more how vnodes can improve availability, proc and cons of all the strategy.
Section partitioning discuss all the three options and difference between them, also point out when to use Murmur3Partiotion and the benefit of the ByteOrderedPartitioner. Understanding of these fundamentals will help readers to scale cluster effectively.
Chapter 3: Replication
Chapter provide fundamental concepts of replication and consistency of Cassandra cluster. Author demonstrate relation between replication and various consistency level and how they impact on Cassandra performance and data consistency. From my point of view very interesting part is the ,which can be very useful to make decision for deploy very wide range of cluster.
Chapter 4: DataCenter
Datacenter or DC one of the basic features for Cassandra high availability. Chapter provides all the possible use cases to use multiple data centers. One on the most important part of this chapter is the replication across data centers, where author describe the consistency in a multiple data centers. Also chapter covers how to setup multiple data centers and analysis data through Hadoop and spark.
Chapter 5: Scaling out
Chapter focused on scaling of Cassandra cluster, provide information for hardware sizing. Chapter base on all the valuable information of how to setup cluster, add nodes and decommissioning of node on the cluster. All of the administrative information's is very useful for any Cassandra administrator.
Chapter 6: Java Client
Mainly this chapter dedicated for developer and author provides all the necessary information to develop high available application based on Cassandra. Most of the code snippet based on Data stax native java client and graceful show how to connect to cluster, using asynchronous request and using failover policy. Chapter shows most of all the wealthy functionality of native client. For the Cassandra beginners current chapter might be the quick start point.
Chapter 7: Modeling for high availability
Chapter bases on the Cassandra Data model, author successfully describe the Cassandra's low level storage model. Author provides information every level of compaction and how compaction works under the hood. Even more, explain when and how to use different level of compactation to achieve desired goal. End of the chapter demonstrate how to model time series data and how to work with geospatial data.
Chapter 8: Anitpaterns
To be hones, it's best chapter of this book, which shows why we should not use secondary index and why we shouldn't use Cassandra as a distributed queue. Chapter demonstrate how tomstoms can effect on Cassandra read performace and how to get rid out of it. This chapter can give readers a foundation that will allow to make correct data modeling decision.
Chapter 9: Falling gracefully
This chapter mainly aim to the Cassandra administration and give well defined information for monitoring and management Cassandra cluster. Chapter clearly define all the possible way to monitoring Cassandra, such as through JMX , nodetools or third party tools. End of the part describes backup and restore process of Cassandra which will be very useful for Cassandra administrator.

Comments

Popular posts from this blog

Tip: SQL client for Apache Ignite cache

A new SQL client configuration described in  The Apache Ignite book . If it got you interested, check out the rest of the book for more helpful information. Apache Ignite provides SQL queries execution on the caches, SQL syntax is an ANSI-99 compliant. Therefore, you can execute SQL queries against any caches from any SQL client which supports JDBC thin client. This section is for those, who feels comfortable with SQL rather than execute a bunch of code to retrieve data from the cache. Apache Ignite out of the box shipped with JDBC driver that allows you to connect to Ignite caches and retrieve distributed data from the cache using standard SQL queries. Rest of the section of this chapter will describe how to connect SQL IDE (Integrated Development Environment) to Ignite cache and executes some SQL queries to play with the data. SQL IDE or SQL editor can simplify the development process and allow you to get productive much quicker. Most database vendors have their own front-en

8 things every developer should know about the Apache Ignite caching

Any technology, no matter how advanced it is, will not be able to solve your problems if you implement it improperly. Caching, precisely when it comes to the use of a distributed caching, can only accelerate your application with the proper use and configurations of it. From this point of view, Apache Ignite is no different, and there are a few steps to consider before using it in the production environment. In this article, we describe various technics that can help you to plan and adequately use of Apache Ignite as cutting-edge caching technology. Do proper capacity planning before using Ignite cluster. Do paperwork for understanding the size of the cache, number of CPUs or how many JVMs will be required. Let’s assume that you are using Hibernate as an ORM in 10 application servers and wish to use Ignite as an L2 cache. Calculate the total memory usages and the number of Ignite nodes you have to need for maintaining your SLA. An incorrect number of the Ignite nodes can become a b

Load balancing and fail over with scheduler

Every programmer at least develop one Scheduler or Job in their life time of programming. Nowadays writing or developing scheduler to get you job done is very simple, but when you are thinking about high availability or load balancing your scheduler or job it getting some tricky. Even more when you have a few instance of your scheduler but only one can be run at a time also need some tricks to done. A long time ago i used some data base table lock to achieved such a functionality as leader election. Around 2010 when Zookeeper comes into play, i always preferred to use Zookeeper to bring high availability and scalability. For using Zookeeper you have to need Zookeeper cluster with minimum 3 nodes and maintain the cluster. Our new customer denied to use such a open source product in their environment and i was definitely need to find something alternative. Definitely Quartz was the next choose. Quartz makes developing scheduler easy and simple. Quartz clustering feature brings the HA and