Did SQL Server provide any of the basis for Cosmos DB, or are they two different technologies?
Two completely different technologies. The common thread between them is that they both use Azure components underneath. That's a common layer, but they're both different technologies.
How has Cosmos DB worked out at different user sites that have had preview versions of it? Jet.com was mentioned as an early user.
They've been in production with this for, I think, close to a year.
Is there anything else you want to say about Cosmos DB?
I would say a couple of things worth noting. One is that it is the world's first globally distributed database that supports multiple data models, and it's extensible, so we'll keep adding. It is the first globally distributed database that makes global distribution of data turnkey, meaning you can go with a single click of a button or an API call. There is no setup of machines or datacenters or replication topologies. It's simple. The mission for us is to enable developers to write globally distributed apps easily because we think users would benefit from low latency around the world, high availability, consistency choices, scaling throughput worldwide, all of these things.
And you can count on it because it is backed by very comprehensive SLAs. It's the first time since the arrival of cloud that a service has SLAs that are beyond high availability. Everyone has high availability SLAs, but this has low-latency SLAs, as well as consistency SLAs and throughput SLAs. This is something that a lot of engineering has gone into, so large companies or startups who care about at that scale like Jet.com or some of the other names we have, they can count on it.
Sign up for Computerworld eNewsletters.