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.
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"
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.
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?
> 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.
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.
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.
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).
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
"MongoDB databases are being decimated in soaring ransomware attacks that have seen the number of compromised systems more than double to 27,000 in a day."
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.
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
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.
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?
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).
[+] [-] morghus|9 years ago|reply
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
[+] [-] mat_keep|9 years ago|reply
"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
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
[+] [-] camus2|9 years ago|reply
> 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
[+] [-] flintchip|9 years ago|reply
[+] [-] unknown|9 years ago|reply
[deleted]
[+] [-] verandaguy|9 years ago|reply
[+] [-] laurentdc|9 years ago|reply
[1] https://news.ycombinator.com/item?id=13644789
[+] [-] y0ghur7_xxx|9 years ago|reply
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
[+] [-] zip1234|9 years ago|reply
[+] [-] hoodoof|9 years ago|reply
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
Does serverless somehow mandate a non SQL solution?
[+] [-] cyberferret|9 years ago|reply
Thinking of setting up an EC2 instance running RethinkDB or PouchDB for my project (and for future projects).
[+] [-] ZGF4|9 years ago|reply
[+] [-] hayd|9 years ago|reply
why?
[+] [-] steve918|9 years ago|reply
[+] [-] etoykan|9 years ago|reply
[+] [-] ZGF4|9 years ago|reply
[+] [-] searchfaster|9 years ago|reply
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
[+] [-] supremesaboteur|9 years ago|reply
In response to https://www.theregister.co.uk/2017/01/09/mongodb/ ?
"MongoDB databases are being decimated in soaring ransomware attacks that have seen the number of compromised systems more than double to 27,000 in a day."
[+] [-] unknown|9 years ago|reply
[deleted]
[+] [-] alexyoung|9 years ago|reply
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
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
[+] [-] vikestep|9 years ago|reply
[+] [-] dirkg|9 years ago|reply
I think that's a first, right?
[+] [-] redwood|9 years ago|reply
[+] [-] willvarfar|9 years ago|reply
[+] [-] fergie|9 years ago|reply
[+] [-] doublerebel|9 years ago|reply
[+] [-] al2o3cr|9 years ago|reply
[+] [-] rdiddly|9 years ago|reply
[+] [-] trustfundbaby|9 years ago|reply
[+] [-] blablabla123|9 years ago|reply
[deleted]
[+] [-] unknown|9 years ago|reply
[deleted]
[+] [-] z0noxz|9 years ago|reply
[+] [-] Oletros|9 years ago|reply
[+] [-] joe563323|9 years ago|reply
[+] [-] bpicolo|9 years ago|reply
[+] [-] unknown|9 years ago|reply
[deleted]