So I've run Cassandra on both Aws and azure. I would strongly suggest that if you have the option, run as far away from azure as you can.
Here's a list of issues I have running Cassandra on azure: 1. No native snitch 2. No concept of availability zones. This makes it impossible for Cassandra to put replicas in different AZs. This will hurt your uptime and might incur loss of data. (They have something called a fault domain tho) 3. The disks have iops that land in the floppy disk range 4. Even running SSDs will give you poor performance. 5. Beware of the global storage account limit. This makes scaling out hurt performance if you put them on the same storage account. Which if your using images is your only choice. Sent from my iPhone > On 4 nov. 2016, at 00:22, cass savy <casss...@gmail.com> wrote: > > I would like to hear from the community on their experiences or lesson learnt > on hosting Cassandra in cloud platforms like > > 1. Google Cloud Platform > 2. AWS > 3. Azure > > 1. Which cloud hosting is better and Why? > 2. What differences of C* over vendor provided NoSQL DB like (Bigtable, > Dynamo,Azure Document DB) > 3. AWS is more mature in his offerings and Azure is getting there or its > there already based on what I have been investigating so far? > > 4. What is drive to pick one vs another -Is it cost, infrastructure, hardware > SKU, availability, scalability, performance,ease of deployment and > maintenance,..etc? > > Please let me know your thoughts and suggestions if somebody has done a deep > dive into these 3 cloud platforms for C*. > > > We use datastax cassandra and exploring new usecases in AWS and also > evaluating or POC it in Azure/GCP >
