Azure Cosmos DB, a globally distributed database • Hacker News Board

Re: Azure Cosmos DB, a globally distributed database

#21

Post by martinknafve » Wed, May 10, 2017, 4:39 PM UTC

oedenfield wrote: post #19

martinknafve wrote: post #11

No backup/restore?

Backup is automatic and restore is available within a time frame. https://docs.microsoft.com/en-us/azure/documentdb/documentdb...

> If the data is accidently dropped or corrupted, please contact Azure support within 8 hours

Thats sounds less then optimal. :)

Re: Azure Cosmos DB, a globally distributed database

#22

Post by oedenfield » Wed, May 10, 2017, 4:39 PM UTC

chaostheory wrote: post #6

Is it open source? Why do I care? The same reason I don't use AWS or Google Cloud only datastores: I want to avoid vendor lockin.

See the news about Azure Database for MySQL and Postgresql https://azure.microsoft.com/en-us/services/postgresql/ https://azure.microsoft.com/en-us/services/mysql

Re: Azure Cosmos DB, a globally distributed database

#23

Post by martinknafve » Wed, May 10, 2017, 4:41 PM UTC

bpicolo wrote: post #14

martinknafve wrote: post #11

No backup/restore?

They guarantee durability. I imagine that's a part of it? I guess no backup/restore is a problem if you manage to delete all your data, so we'd have to see some docs, heh

At some point someone will accidentally overwrite or delete data and discover that some days later...

Re: Azure Cosmos DB, a globally distributed database

#24

Post by dmarlow » Wed, May 10, 2017, 4:44 PM UTC

I want a competitor to Google Cloud SQL in Azure.

Re: Azure Cosmos DB, a globally distributed database

#25

Post by yazaddaruvala » Wed, May 10, 2017, 4:45 PM UTC

jasondc wrote: post #4

> Latency: 99.99% of Impressive SLA to guarantee, I'm curious if this will hold up in all random customer workloads that are coming, e.g. updating a lot of fields in a large document (or just a very large insert).

"For a typical 1-KB item, Cosmos DB guarantees end-to-end latency of reads under 10 ms and indexed writes under 15 ms at the 99th percentile, within the same Azure region."

i.e. 1 KB item; Same Azure region;

This now seems more plausible.

One thing I'm curious about is if they tested load on a single partition, or if they only tested latencies for random access.

Re: Azure Cosmos DB, a globally distributed database

#26

Post by henriksen » Wed, May 10, 2017, 4:50 PM UTC

Talk about the foundations of Cosmos DB: https://www.youtube.com/watch?v=Yfmw7swCtZs

Re: Azure Cosmos DB, a globally distributed database

#27

Post by curiousDog » Wed, May 10, 2017, 4:52 PM UTC

dmarlow wrote: post #24

I want a competitor to Google Cloud SQL in Azure.

It's called Azure SQL DB (unless you want Mysql, then you'd want IaaS SQL DB)

Re: Azure Cosmos DB, a globally distributed database

#28

Post by dmarlow » Wed, May 10, 2017, 4:58 PM UTC

curiousDog wrote: post #27

dmarlow wrote: post #24

I want a competitor to Google Cloud SQL in Azure.

It's called Azure SQL DB (unless you want Mysql, then you'd want IaaS SQL DB)

With the exception that Azure SQL doesn't horizontally scale across regions/datacenters like Google Cloud SQL does.

Re: Azure Cosmos DB, a globally distributed database

#29

Post by VikingCoder » Wed, May 10, 2017, 4:59 PM UTC

I'd like to see an in-depth comparison with Google Cloud Spanner.

Re: Azure Cosmos DB, a globally distributed database

#30

Post by aliostad » Wed, May 10, 2017, 5:07 PM UTC

sealord wrote: post #5

judah wrote: post #2

This isn't a new database. This is a rebranding of the generically-named Azure DocumentDB, plus some new features.

Not exactly. DocumentDB was primarily a document store. Cosmos allows you to store graphs and KV pairs as well.

DocumentDB is KV.