Slashdot Mirror
Azure Goes Database Crazy With One New NoSQL, Two New SQL Services (arstechnica.com)
An anonymous reader quotes a report from Ars Technica: In its continued efforts to make Azure a platform that appeals to the widest range of developers possible, Microsoft announced a range of new features at Build, its annual developer conference. Many of the features shown today had a data theme to them. The most novel feature was the release of Cosmos DB, a replacement for, or upgrade to, Microsoft's Document DB NoSQL database. Cosmos DB is designed for "planet-scale" applications, giving developers fine control over the replication policies and reliability. Replicated, distributed systems offer trade-offs between latency and consistency; systems with strong consistency wait until data is fully replicated before a write is deemed to be complete, which offers consistency at the expense of latency. Systems with eventual consistency mark operations as complete before data is fully replicated, promising only that the full replication will occur eventually. This improves latency but risks delivering stale data to applications. Document DB offered four different options for the replication behavior; Cosmos DB ups that to five. The database scales to span multiple regions, with Microsoft offering service level agreements (SLAs) for uptime, performance, latency, and consistency. There are financial penalties if Microsoft misses the SLA requirements. Many applications still call for traditional relational databases. For those, Microsoft is adding both a MySQL and a PostgreSQL service; these provide the familiar open source databases in a platform-as-a-service style, removing the administrative overhead that comes of using them and making it easier to move workloads using them into Azure. The company is also offering a preview of a database-migration service that takes data from on-premises SQL Server and Oracle databases and migrates it to Azure SQL Database. Azure SQL Database has a new feature in preview called "Managed Instances" that offers greater compatibility between on-premises SQL Server and the cloud variant, again to make workload migration easier.
The Check cleared the bank, thanks!
Yours, Slashvertisement team
If I want to try out Cosmos DB I have to pay an Azure subscription? As I can see, it's not a stand-alone product at all.
I'm glad that an established company is building out solid PaaS offers. Does anyone really believe that the company that sells 55 gallon lube tubs can offer the same reliability that Microsoft can?
Planet-scale, eh? I can tell you already the answer is 42.
.
Azure may be the greatest thing since sliced bread, but it will always suffer from the anchor that is the Windows 10 update disaster.
Planet-Scale databases? Sounds like they've already started loading their database with everyone's Windows 10 data and metadata. Since they couldn't be bothered to generate any FAKE data, this one's considered a "live fire" test.
Don't you just hate it when the Whole Planet BSODs though? It takes real expert to generate that sized mess.
?? So can you generate a BLOB the size of a planet? If so, that would explain the old joke about "You can't own everything in the world since there'd be no place to put it." I guess tape backups really ARE dead.
If the universe is someone's simulation -- does that mean the stars are just stuck pixels?
I'm not going to read articles written by children.
You aren't going to care about the tiny financial penalty, which will be part of your money you are paying for the database-as-a-service, when your entire business does not function because Azure went down. It won't even begin to cover your losses.
Azure is one of the worst cloud services in terms of downtime historically. They all get downtime sometimes, but if you are going to sell out to the cloud don't use this one.
It's actually called Cosmo's DB. It was invented by the guy with the weird hair from Seinfeld.
I hate all these microsoft advertisement low quality shit.
I don't recognize you Slashdot
Don't use this piece of garbage.
Performance is abysmal, cost sky-high (for decent read/write performance in a single collection, you're looking at over $1,000/mo, and that's for data sets under 10 GB because if you go over 10 GB it forces you to partition the data, which dilutes performance between the partition shards), there is no proper tooling (unless you count the Azure "portal" which is a series of perpetual slow or failed AJAX requests), poor SDK, and lacking basic features (e.g. update part of a document, backup/restore). Last but not least, it locks you into the Azure platform.
Maybe in 5 years it will become somewhat respectable, just like how MongoDB took a while to gain traction and stability. For now, steer clear.
Planet-Scale databases? Sounds like they've already started loading their database with everyone's Windows 10 data and metadata.
Nope... they've started loading it with my distributed peer-to-peer statistical noise data generation system. Muhahahaha. Big data. Yep, it's big, a big steaming pile of useless... bits.
We'll make great pets
Don't you just hate it when the Whole Planet BSODs though?
We call it the Blue Planet for a reason, you know.
>> Azure Goes Database Crazy With One New NoSQL, Two New SQL Services
The best part about standards is that there are so many different ones to choose from. Wheee!
I just use KirbyCMS, which is faster than any database because it runs off the native filesystem, and provides me tools that most databases simply cannot or do not provide.
Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
Now that they found a way to charge for it, they are totally jumping on the bandwagon.
Sarcasm aside, this could be good if they contribute code for better performance or scalability to the projects. Then again, their code could be so tightly coupled to the Azure infrastructure that it is useless to anyone else. I don't really follow those projects to know if that's happening though.
---
According to the latest ruleset, this post should be modded as Vorpal Flamebait +5.
Who in their right mind would trust business-critical data to Microsoft? Honestly? It makes no sense. Surely no respectable devops person would allow this. Is this 'Cosmos DB" even open source? How does anyone know what it's doing with their data? Microsoft seriously needs to get out of this market.