I will recommend against this idea. And here is why (at a higher level of
abstraction)
1. This means the cloud services aren't reliable in the first place. That
itself is a big problem. Else with reliability guarantees and
multi-region/zone it should be pretty safe to stay in one place.
2. Devil is
Hello all
I've given a thought to this multi-cloud marketing buzz with Cassandra
Theoretically feasible (with GossipingPropertyFileSnitch) but practically a
headache if you want a minimum of performance and security
The problem comes from the network "devils in the details"
Suppose DC1 in AWS i
Thanks Jon that explained me everything.
On Thu, Sep 5, 2019 at 10:00 AM Jon Haddad wrote:
> Technically, not a problem. Use GossipingPropertyFileSnitch to keep
> things simple and you can go across whatever cloud providers you want
> without issue.
>
> The biggest issue you're going to have is
Technically, not a problem. Use GossipingPropertyFileSnitch to keep things
simple and you can go across whatever cloud providers you want without
issue.
The biggest issue you're going to have isn't going to be Cassandra, it's
having the expertise in the different cloud providers to understand the
you can build cassandra under multi cloud environment ,but there network
can be connect with each other.☺
Goutham reddy 于2019年9月6日周五 上午12:36写道：
> Hello,
> Is it wise and advisable to build multi cloud environment for Cassandra
> for High Availability.
> AWS as one datacenter and Azure as another
Hello,
Is it wise and advisable to build multi cloud environment for Cassandra for
High Availability.
AWS as one datacenter and Azure as another datacenter.
If yes are there any challenges involved?
Thanks and regards,
Goutham.
