This article is the second of the series about configuring a Cassandra Cluster in Azure. In the previous one we completed the installation of Cassandra in a new Virtual Machine (VM) in Azure, this VM will become our template for creating new nodes based on it.  In this article we will be covering the next sections:

• Localize key files
• Configuring our Cluster (cluster name, seed nodes)
• Adding more configuration to Cassandra through yaml file
• Configuring RPC (service, interface, and address)
• Deleting data directory

The Apache Cassandra Database is one of the most growing and so scalable NoSQL technology available in the market with an increasing number of companies around the world using it.  Every time that I start a new professional journey toward learning a new technology, It is so important to me count with the tools and a puppet project which give me the possibility to start practicing and including a realistic scenario where I would have the opportunity of consolidating any new knowledge acquired, hence having a Cassandra Cluster with many nodes is must, mainly because horizontal scaling is one of the main strengths of Cassandra. 

This article is part of a series dedicated to showing some examples of Databases common problem and how to address it, this time the turn is for MySQL, a great RDBSM and extremely popular relational system. Here the link to the blog of my company TheWorkshop where I decided to contribute with this series of articles, I hope you enjoy it.

https://theworkshop.com/es/blog/how-to-load-millions-of-rows-into-mysql-without-agony/

Recently I completed an intensive course on CodeSpace academy where I taught students about Database fundamentals, it was an enjoyable time, that I normally repeat every year. Maybe are you asking yourself why I consider this activity as a hobby, my answer is simple, I really love to teach and share my knowledge with others, especially when some people are struggling day to day to improve their personal-professional career.