It is good enough if you do not care about automation.
If you care about automation (and you really should), GossipPropertyFileSnitch
is not good enough as it has to be manually updated. Same with availability
set, fault domain isn't available for the instance as metadata as it is on
AWS.
You stil
Hi,
>1. No native snitch
It's not great problem. GossipPropertyFileSnitch is good enough.
>2. No concept of availability zones.
Azure does have such concept - Availability Set. It provides three fault domain
(availability zone in Amazon terms) and 20 updates domains.
>4. Even running SS
Also, if you're running it on azure you should have a look at Netflix Priam.
That really helped us automate stuff.
Dynamo db works well if you don't want to spend hours in running your cluster.
If I were to have the option to run on AWS I would use Dynamo when possible.
Sent from my iPhone
>
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
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 Docu
