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 aravindkr1 on Wednesday May 10, 2017 @04:21PM (#14311292)
One key difference is the cost difference between running Cosmos DB and Cassandra. We have a TCO paper (https://aka.ms/documentdb-tco-paper) that shows that for a 1M operations/second workload, Cosmos DB is significantly 3x-10x cheaper than other systems.
[ Parent | on HN ]
Re:Azure Cosmos DB, a globally distributed database by brianwawok on Thursday May 11, 2017 @07:56AM (#14315346)
And white papers are full of it. Has random things like s Cassandra cluster needs 1 full time engineer per 100 nodes. Where do you come up with this stuff?
[ Parent | on HN ]
Re:Azure Cosmos DB, a globally distributed database by throwanem on Thursday May 11, 2017 @09:36AM (#14315865)
In my experience of Cassandra (working on an application client, not managing it), one FTE per hundred nodes is extremely generous.
[ Parent | on HN ]
Re:Azure Cosmos DB, a globally distributed database by bshanks on Thursday May 11, 2017 @02:11PM (#14318206)
Do you mean that you typically need more engineers, or less?
[ Parent | on HN ]
Re:Azure Cosmos DB, a globally distributed database by throwanem on Thursday May 11, 2017 @02:24PM (#14318304)
The former. One FTE per dozen nodes is more in line with what I've seen in practice.
[ Parent | on HN ]