top | item 13665695

Dear MongoDB users, we welcome you in Azure DocumentDB

126 points| jeremya | 9 years ago |azure.microsoft.com | reply

108 comments

order
[+] morghus|9 years ago|reply
Yes, except you can't do the most basic things with DocumentDB and it becomes very expensive very fast. Especially if you want multiple collections.

There's a lot lacking with DocumentDB, as evident from the feedback forum, that comparing it to Mongo is like comparing an infant to an adult. The infant might be cute, but it can't do a whole lot.

https://feedback.azure.com/forums/263030-documentdb/filters/...

[+] youdontknowtho|9 years ago|reply
To build something similarly sized with the free version of Mongo would also be expensive. It's a trade off.
[+] mat_keep|9 years ago|reply
When users have evaluated DocumentDB against MongoDB, they see major shortcomings in Microsoft's offering:

"As we were developing our new financial benchmarking service last year, we evaluated Microsoft’s Azure DocumentDB, but MongoDB offered much richer query and indexing functionality"

KPMG France https://www.mongodb.com/blog/post/kpmg-france-enters-the-clo...

[+] redwood|9 years ago|reply
All of the following three share something in common: 1) Microsoft Azure DocumentDB 2) Google Cloud Spanner 3) Amazon Web Services DynamoDB

Total cloud-vendor lock-in. It's clear why the clouds want users investing in these difficult-to-migrate-from solutions...

[+] curiousDog|9 years ago|reply
Needs more hashtags. Reach all those Millenials graduating $10k 3-month bootcamps. Sigh.
[+] camus2|9 years ago|reply
lol, yeah, this marketing piece doesn't really feel professional. It is littered with useless illustrations and bad poetry.

> Third, we do it with love…

With love for our money sure. What the hell does that even mean? I really rolled my eyes reading that blog post. This is childish and out of place for an article trying to sell security.

[+] fb03|9 years ago|reply
It's really satisfying when I read some post with what I exactly wanted to write but didn't have the balls to. Thank you :)
[+] flintchip|9 years ago|reply
What a sweeping generalisation to make.
[+] verandaguy|9 years ago|reply
I've been out of touch with Mongo for a while, but when did it stop being common practice to just hide :27017 behind a firewall with only your app's DB access layer (or, at most, a few nodes in the local subnet) talking to it?
[+] y0ghur7_xxx|9 years ago|reply
> hide :27017 behind a firewall with only your app's DB access layer talking to it?

Because if you can do without it, why bother? Developing an access layer costs time and money. If you can leverage the DB features to do what you need, you can make you stack simpler and more maintainable.

[+] ec109685|9 years ago|reply
One of the best things about AWS is the "Jeff Barr style" posts describing every service they release. I find them much easier to consume than a blog post like this.
[+] zip1234|9 years ago|reply
Well, this post was a marketing post, not a product release. Product release posts in Azure are much more informative for a dev that this post.
[+] hoodoof|9 years ago|reply
AWS needs something like this.

The missing piece for the AWS serverless story is a database that is suitable for writing real world applications. DynamoDB is far from suitable for that task, which leaves AWS serverless with no good database.

[+] kiallmacinnes|9 years ago|reply
AWS has RDS - That's most certainly a database suitable for writing real world applications as its MySQL.

Does serverless somehow mandate a non SQL solution?

[+] cyberferret|9 years ago|reply
Yeah, I dabbled in DynamoDB for a recent project - couldn't really get my head around it - very strange sort of NoSQL database. The query language is incredibly arcane and wordy, and mostly inflexible.

Thinking of setting up an EC2 instance running RethinkDB or PouchDB for my project (and for future projects).

[+] ZGF4|9 years ago|reply
Cross datacenter replication is the missing piece from AWS. I wish they'd just roll out a hosted Cassandra or something identical
[+] hayd|9 years ago|reply
> DynamoDB is far from suitable for that task

why?

[+] steve918|9 years ago|reply
DynamoDB would be pretty close if it just allowed null values.
[+] etoykan|9 years ago|reply
I think Microsoft should implement basic aggregation functions first.
[+] ZGF4|9 years ago|reply
Implementing aggregation at query time is a temporary solution. For systems like this aggregation should be done on insert time - many hugely popular databases do not provide much more than a basic get operation for this reason
[+] searchfaster|9 years ago|reply
Interesting... So compatible with Mongodb protocol but not using mongodb internally ?

What is your view of services, which provide functionality of some other software or SAAS and is API / Protocol compatible ?

Can API / protocols be copyrighted or patented? I believe not based on Google vs Oracle.

[+] willvarfar|9 years ago|reply
Hasn't tokuMX already put a 'proper' solid DB behind the mongo API?
[+] alexyoung|9 years ago|reply
As someone that almost got bitten by MongoDB's lax auth defaults, I was happy to read that DocumentDB has enabled access control out of the box and no default username/password.

Also, there's a query playground if you want to try it out quickly: https://www.documentdb.com/sql/demo

[+] raverbashing|9 years ago|reply
It's important to be aware of security implications of leaving an unauthenticated server listening on the open internet (listening on 0.0.0.0 is not the default since some time now and if installing the rpm/deb package listening on 127.0.0.1 is the default option). Also never leave an internet facing server without a firewall.

As a SaaS it's not surprising DocumentDB got security configured, and it also won't be surprising when people lose data because they'll put '123456' as their password or commit their password to a public repository

[+] EpicEng|9 years ago|reply
Of course, you really shouldn't be exposing databases if you don't know how to administer them. I agree that the defaults should be better, but...
[+] vikestep|9 years ago|reply
We used to use DocumentDB, but switched to Azure Table Storage a while back. Did some benchmarking and DocumentDB was too slow for our needs (getting documents for a range between two epochs). Not sure if others experienced the same thing or if things have gotten better since then though.
[+] dirkg|9 years ago|reply
Never looked at DocumentDB before. So if I get this straight, I can get a fully managed DB that can scale easily, but still have all the advantages and compatibility of a regular NoSQL like Mongo?

I think that's a first, right?

[+] redwood|9 years ago|reply
Except that the advantages and compatibility are not all there. Plus there are now fully managed options for the real thing.
[+] willvarfar|9 years ago|reply
Percona have their drop-in MongoDB replacement that uses TokuMX under the hood and they'll manage it for you.
[+] fergie|9 years ago|reply
Isn't it the same general idea as Amazon's DynamoDB?
[+] doublerebel|9 years ago|reply
Fully managed easily scalable nosql DBs have been available for many years as CouchDB variants from multiple providers.
[+] al2o3cr|9 years ago|reply
I hear it's got even better write performance than /dev/null ;)
[+] rdiddly|9 years ago|reply
Potter's paying 50 cents on the dollar for your shares in the Building & Loan...
[+] z0noxz|9 years ago|reply
Trading privacy for a false sense of security, are we?
[+] Oletros|9 years ago|reply
Trading privacy? Can you elaborate?
[+] joe563323|9 years ago|reply
Microsoft trying hard to get developers to work on their platform and fail has really become very much fun. Microsoft deserves for being evil. Example: Microsoft does not save history in cmd shell(its so irritating for devs). The height of the cruelty is they aliased the curl and wget by default to its own program(do not remember).
[+] bpicolo|9 years ago|reply
Having a subpar shell application is evil?