101–110 of 119 posts
Earlier quoted context omitted.
The advantages are real. Compatibility might not be 100%, but honestly Mongo isn't magic. DocumentDB has strengths of it's own.
I'd be happy to learn about your experience developing an application against DocumentDB and its strengths. Care to share?
Needs more hashtags. Reach all those Millenials graduating $10k 3-month bootcamps. Sigh.
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.
Cross datacenter replication is the missing piece from AWS. I wish they'd just roll out a hosted Cassandra or something identical
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?
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
Earlier quoted context omitted.
https://www.microsoft.com/en-us/TrustCenter/Privacy/default.... If you don't trust MS you can trust one of the organisations that certified them for the strictest compliance and regulations in the public cloud space.
Sounds good. But how do you exactly verify those claims? Again, you can't. You are back to square 1: trusting Microsoft acts in good faith and acts in your best interest.
Earlier quoted context omitted.
When has a SaaS operator stolen data hosted on their service?
Not agreeing with thread OP here, but I would certainly differentiate between "stealing" and "exploiting" (not in a security exploit sense). User data certainly gets exploited on _some_ SaaSs that would otherwise be unexploitable on your own stack. I'm not saying this necessarily applies to compute engines or storage as a service or whatever, but something like gmail (SaaS) where your data is used to target ads at yo…
If Google, Microsoft or other companies start to look at the data to exploit it hey will lose trust, the customers and the data.
Earlier quoted context omitted.
> 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.
It does not take that much time or effort to set up useful subnet/vpc security in AWS. Put the database in your VPC, say only your application vpc can talk to it. Done. Reasonably good security practices are not that much effort, and really it's a case for respecting your users for the most part. The security trust game is starting to blow up. Yahoo just lost $250million dollars to it.
Earlier quoted context omitted.
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.
> Product release posts in Azure are much more informative for a dev [than] this post. Who is this for then?
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
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 surp…
Personally, I'm pretty happy with how easy it is to use the Azure Storage services (blob, tables, queues) as well as their Azure SQL offering. Far less arcane configuration options than you get with AWS's competing options. If only their compute nodes weren't so pricey.