Live data from Hacker News

Amazon DocumentDB, with MongoDB compatibility

aws.amazon.com

111–120 of 323 posts

Re: Amazon DocumentDB, with MongoDB compatibility

#111
post #2

Finally an AWS service where the name makes sense and describes what it is. I hope this is the start of a trend.

Yeah, they copied Azure basically. DocumentDB was the name of an Azure service in past, interestingly it offered MongoDB, Gremlin and other API gateway options. Its called Azure CosmosDB now.

Re: Amazon DocumentDB, with MongoDB compatibility

#112

How the heck was this approved by legal? AWS is linking to MongoDB's own documentation. https://docs.aws.amazon.com/documentdb/latest/developerguide... Go to any operation, it links to docs.mongodb.com !

Nothing novel here by Amazon. Azure had MongoDB gateways (and many others) for their NoSQL offering.

Re: Amazon DocumentDB, with MongoDB compatibility

#113
post #64
post #5

Earlier quoted context omitted.

I love Azure for this. The names are almost all extremely straightforward. There are a handful that have made the jump from confusing to straight forward, and a handful that have made the jump from straightforward to confusing (CosmosDB, formerly DocumentDB, chiefly comes to mind).

Except for the fact that Azure names seem to change once per year. Our Azure SA was giving us a presentation and actually got confused himself. "So that's TFS... I mean VSTS... Actually wait, it's Azure DevOps now?"

Just wait until next year when it’s called TFSHub.

Re: Amazon DocumentDB, with MongoDB compatibility

#114
post #77

Earlier quoted context omitted.

MongoDB still have a strong hand - control of the client and particularly its exposed featureset - due to that, also control of the protocol and the ability to, for example, insert legally protected strings in the style of the Apple SMC signature into the handshake. - ability to gate new features on the presence of an object like a copyrighted text, trademark, or even a crypto signature - ownership of the name. AWS a…

The client change would never work. The client is licensed as lgpl, so if they tried to pull any funny business like that, it would be instantly forked and if’d out.

As the person suggesting it, it's difficult to imagine how it could never work considering I haven't managed to figure out all the possible combinations in which such a strategy could be applied. Finally, it is quite exasperating to call this kind of strategy "funny business" in a thread about their core tech being ripped off by a megacorp

Re: Amazon DocumentDB, with MongoDB compatibility

#116
post #79

I was reading a post [0] by Brian Cantrill that predicted this would be the result of licences like the SSPL. I instinctively disagreed with him, but it turns out he was right: "The cloud services providers are currently reproprietarizing all of computing — they are making their own CPUs for crying out loud! — reimplementing the bits of your software that they need in the name of the service that their customers want…

What is the way out? Would love to hear from people.

There's no secret formula to stop people from competing with you. If MongoDB Inc is successful, it should be because they run a good document-database-as-a-service people want to use, not because they earn indefinite seigniorage from launching a popular open source project.

Re: Amazon DocumentDB, with MongoDB compatibility

#117

I hope MongoDB's users are really keen on on-prem otherwise this might be a challenging moment for them.

Not sure what this means. MongoDB has had Atlas which is a cloud hosted solution for a while now.

Poster means that their cloud business could be impacted, but on-prem (non aws) would not be.

Re: Amazon DocumentDB, with MongoDB compatibility

#119
post #106

Earlier quoted context omitted.

Besides that AWS will charge per transaction (at 0.2 per million) outrageous given that you already pay per instance. Correct pricing strategy needs to be per request or per instance, AWS is charging for both

The correct pricing strategy of any product is "whatever the customer is willing to pay for it". If you feel the price is too steep for your use-case, then don't buy it.

That's rarely actually true for anyone that wants to operate for more than a short time period. There are significant costs to gouging your customers. Anything from it being illegal, to it encouraging competition and your customers being motivated to actively flee you and shit on your reputation. The correct pricing strategy for people that don't have a long term enforceable monopoly is "whatever most customers are willing to reasonably happily pay"

Re: Amazon DocumentDB, with MongoDB compatibility

#120

My bet is that it is built on top of Aurora PostgreSQL. By looking at the "Limits" section ( https://docs.aws.amazon.com/documentdb/latest/developerguide... ), identifiers are limited to 63 characters and the same characters that PostgreSQL limits identifiers to; and a collection size limit of 32TB, coincidentally maximum PostgreSQL table size. Edit: I can confirm: does not allow the UTF-8 null character in strings:…

Wasn’t latest Mongo built on Postgres backend too?
Post reply on HN