Avoid Vendor Lock-In Risk with Multi-Cloud Deployments

Re:Avoid Vendor Lock-In Risk with Multi-Cloud Deployments by caleblloyd on Wednesday October 04, 2017 @08:45PM (#15406019)

I think this is a poorly written blog post that completely ignores the challenges and difficulties that arise when going multi-cloud. Multi-cloud introduces huge amounts of latency, requires additional load balancing and routing logic, requires twice as much administration, etc.

Multi-cloud is a huge decision that need lots of planning and application level support. I'd go so far as to say it is an order of magnitude easier to design an application that can be moved between clouds easily than it is to design a multi-cloud application. This still defeats vendor lock-in.

I think CockroachDB is interesting tech, but this blog post reads like a pretty empty marketing piece.

[ Parent | on HN ]

Re:Avoid Vendor Lock-In Risk with Multi-Cloud Deployments by jchanimal on Thursday October 05, 2017 @12:44PM (#15410588)

It’s true that operating your own cluster (of any technology) spanning cloud providers is not for the faint of heart. However, at FaunaDB we’ve found performance of multi-cloud globally consistent operations to be acceptable. We currently run across AWS and GCP, with Azure on the way, and we have customers running their own clusters in hybrid configurations.

[ Parent | on HN ]