News for hackers. Stuff that matters.

A comment on Azure Cosmos DB, a globally distributed database. Parent comment

Re:Azure Cosmos DB, a globally distributed database by yazaddaruvala on Wednesday May 10, 2017 @12:45PM (#14309602)
"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.

[ Parent | on HN ]
Re:Azure Cosmos DB, a globally distributed database by ChuckMcM on Wednesday May 10, 2017 @04:50PM (#14311591)
It is interesting that given their scale it essentially says that you can implement twitter on one of these and be done with a chunk of the infrastructure.
[ Parent | on HN ]
Re:Azure Cosmos DB, a globally distributed database by aravindkr1 on Wednesday May 10, 2017 @04:17PM (#14311267)
Cosmos DB guarantees both low latency and that you can achieve your provisioned throughput with SLAs. Latency is guaranteed at p99 regardless of storage size or number of partitions.
[ Parent | on HN ]
Re:Azure Cosmos DB, a globally distributed database by yazaddaruvala on Wednesday May 10, 2017 @10:42PM (#14313508)
Sorry, I'm not talking about "number of partitions" but if I "forcibly"[0] hit the same partition, will the SLA hold?

[0] i.e. If I somehow pick keys which are on the same partition.

[ Parent | on HN ]