News for hackers. Stuff that matters.

A comment on Azure Cosmos DB: Microsoft's Cloud-Born Globally Distributed Database. Parent comment

Re:Azure Cosmos DB: Microsoft's Cloud-Born Globally Distribu... by silverlake on Sunday April 14, 2019 @10:53AM (#19659738)
He's talking about building the underlying failover mechanism for CosmoDB. For a customer it's easy and automatic, but GCP and AWS and Azure have to build it first.
[ Parent | on HN ]
Re:Azure Cosmos DB: Microsoft's Cloud-Born Globally Distribu... by suff on Sunday April 14, 2019 @01:15PM (#19660493)
Surely you're referring to Microsoft's team's time to implement failover to the product offering, not time every customer spends on implementation???

FTA: "if _you_ are an engineer working on a small thing, say datacenter automatic failover component" (emphasis added). Pretty sure he's talking about EVERY customer spending months to turn on fail-over.

[ Parent | on HN ]
Re:Azure Cosmos DB: Microsoft's Cloud-Born Globally Distribu... by samdixon on Sunday April 14, 2019 @01:54PM (#19660697)
The previous poster is correct, I think you are mistaken. It should read like this:

"if you are an engineer at Microsoft working on a small azure component, say datacenter automatic failover component"

At least this is how I read it since the OP works at MS it appears.

[ Parent | on HN ]
Re:Azure Cosmos DB: Microsoft's Cloud-Born Globally Distribu... by rad_gruchalski on Sunday April 14, 2019 @11:20AM (#19659892)
But months?
[ Parent | on HN ]
Re:Azure Cosmos DB: Microsoft's Cloud-Born Globally Distribu... by manigandham on Sunday April 14, 2019 @07:07PM (#19662217)
To build a globally distributed database offering as complex as Cosmos DB with multiple SLA requirements? Can you build it faster?
[ Parent | on HN ]