Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Dear MongoDB users, we welcome you in Azure DocumentDB

azure.microsoft.com

Post reply on HN
Print view View original

111–119 of 119 posts

Re: Dear MongoDB users, we welcome you in Azure DocumentDB

#111

Post by astral303 »

damagednoob wrote: post #78
virmundi wrote: post #12

Earlier quoted context omitted.

I saw that chain too. I guess I do devops differently. Since I'm bootstrapping I don't have money for an ops person. So I've set about learning ufw, let's encrypt, nginx/tls termination to a service only accepting local connections to the port, etc. I see devops as the developer learning the ops side to take responsibility for the whole stack.

As a dev, I've been going through the same process for several months now. Honestly, for each of the concepts I've come across (ufw, let's encrypt, etc), you might bang your head for a few days with each one but you will eventually get it . I don't know why people make it out to be so difficult.

Stigma around ops and QA work.

Re: Dear MongoDB users, we welcome you in Azure DocumentDB

#112

Post by badminton1 »

EpicEng wrote: post #106
badminton1 wrote: post #60

Earlier quoted context omitted.

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.

How do you verify that a doctor is making the right call re how to treat your cancer? You either become a doctor yourself, or trust that they know what they're doing.

And what if a doctor has a controversial reputation?

Re: Dear MongoDB users, we welcome you in Azure DocumentDB

#113

Post by danek »

lostcolony wrote: post #84
tech2 wrote: post #56

Earlier quoted context omitted.

The price for that 160k is horrifying though, esp. if the requirement is bursty rather than continuous.

Which is why you turn the knob back down when you stop being bursty. But yes, it's pricy. It may not be the best fit for some. Hopefully by the time you're taking 160k writes per second you have a solid business model. I mean, Twitter peaked at around 8000 tweets per second. What are you doing that requires 160k, and do you really need to be storing it?

It's probably an indication that your use-case is not a good fit for dynamo, or that you didn't adapt your use-case to dynamo, you're doing something "wrong" like trying to use it as a relational database. I've experienced some of these pains as part of my dynamo learning curve.

For example by changing my query strategy I was able reduce the provisioned write units from 1900 to 150 (write units dominate the cost).

Re: Dear MongoDB users, we welcome you in Azure DocumentDB

#114

Post by [deleted] »

willvarfar wrote: post #28
badminton1 wrote: post #26

You cannot look at the code, and cannot monitor the infrastructure. The only thing left is trust. Trust in the belief that Microsoft will act in your best interest regarding the privacy of your data. But, isn't reasonable then to ask if Microsoft is actually trustworthy? PRISM, NSAKEY, Flame malware propagating via Windows Update, their 0day policy... I don't think Microsoft is trustworthy.

People choose managed services all the time. If you worry about interception, then code inspection and monitoring isn't going to give you any assurances. You'd have to run open-source software locally, audit it, and not put it on a cloud like Azure in the first place? (And the NSAKEY was something completely different if you dig into it.)

[deleted]

Re: Dear MongoDB users, we welcome you in Azure DocumentDB

#115

Post by joe563323 »

bpicolo wrote: post #90
joe563323 wrote: post #25

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).

Having a subpar shell application is evil?

Aliasing linux command tools to its own is definitively evil https://daniel.haxx.se/blog/2016/08/19/removing-the-powershe...

Re: Dear MongoDB users, we welcome you in Azure DocumentDB

#116

Post by EpicEng »

badminton1 wrote: post #112
EpicEng wrote: post #106

Earlier quoted context omitted.

How do you verify that a doctor is making the right call re how to treat your cancer? You either become a doctor yourself, or trust that they know what they're doing.

And what if a doctor has a controversial reputation?

Then you can make a decision to go with another doctor. Are you questioning the reputation of the auditors, or just writing off MS across the board?

Re: Dear MongoDB users, we welcome you in Azure DocumentDB

#117

Post by badminton1 »

EpicEng wrote: post #116
badminton1 wrote: post #112

Earlier quoted context omitted.

And what if a doctor has a controversial reputation?

Then you can make a decision to go with another doctor. Are you questioning the reputation of the auditors, or just writing off MS across the board?

You can have audit proof software that is completely secure. If you tamper the infrastructure, share keys, leave obscure backdoors, etc. it is not hard to come up with a NOBUS scheme.

Re: Dear MongoDB users, we welcome you in Azure DocumentDB

#118

Post by redwood »

youdontknowtho wrote: post #101
redwood wrote: post #83

Earlier quoted context omitted.

I'd be happy to learn about your experience developing an application against DocumentDB and its strengths. Care to share?

im actually building a fairly well massive app with documentdb and service bus. its not a user facing app, so i dont know if that counts for what you were talking about.

Sure, use case aside - expressiveness or the query language, learning curve, secondary indexing etc - keen to hear how all this feels to a new developer to the platform

Re: Dear MongoDB users, we welcome you in Azure DocumentDB

#119

Post by youdontknowtho »

redwood wrote: post #118
youdontknowtho wrote: post #101

Earlier quoted context omitted.

im actually building a fairly well massive app with documentdb and service bus. its not a user facing app, so i dont know if that counts for what you were talking about.

Sure, use case aside - expressiveness or the query language, learning curve, secondary indexing etc - keen to hear how all this feels to a new developer to the platform

https://channel9.msdn.com/Shows/Azure-Friday/DocumentDB-Supp...
Post reply on HN