6 ms·
Over the last few Months we’ve switched over to amazons document db just to have a managed service. We don’t regret it.
by mikeryan 7y ago
Over the last few
Months we’ve switched over to amazons document db just to have a managed service. We don’t regret it.
- nailer 7y agoDocumentDB is still really expensive as there's no pay what you use option. I stored about 2KB of data for 72 hours and got charged fifteen dollars before I realised the mistake. They really need to come up with a per mb per hour option.
- qeternity 7y agoWhat?!? I’m a big AWS skeptic for most people but this sounds insane. Details?
- smnrchrds 7y agoThe cheapest option is 0.277$/hr just for the instance. https://aws.amazon.com/documentdb/pricing/ https://aws.amazon.com/documentdb/pricing/
- chii 7y agoIt's interesting that people would pay amazon, but not mongodb...
- threeseed 7y agoI work in the enterprise and we spend tens of millions a year with AWS. Our Security, Cloud Engineering and Finance teams understand VPC, IAM, Costs etc back to front and so when you add a new AWS product they know how to manage, secure, finance and support it. And of course there is no Procurement process with adding a new AWS product. With a managed MongoDB (even though it's on AWS) you need to get buy in from dozens of people and go a vendor comparison to get through Procurement. It's why for many companies AWS dominates and in the future could well end up owning everything under the application layer.
- chii 7y agoI guess nobody got fired for buying IBM is still true to this day and age.
- nevi-me 7y agoThis still doesn't sound like a good reason to pay AWS instead of MongoDB. Didn't your Security, Cloud Engineering and Finance teams have no understanding of AWS at some point? Why can't they start to 'understand' how a managed MongoDB works, and give buy-in? There's a common saying we have in our consulting circles, that "Processes should support business, but business decisions shouldn't be made because of lack of processes". We had a large local bank choose not to pursue a good opportunity because "our procurement process takes too long". This instead of investing in fixing the procurement process.
- mbreese 7y agoIf your choice is between (1) get MongoDB support from AWS and (2) get MongoDB support direct from MongoDB, the fact that Security, Cloud engineering and Finance know AWS and how to work in their environment seems to be the obvious choice. The difference between (1) and (2) is probably minimal enough to make the existing relationship with AWS meaningful. I don’t know enough about the costs of the two, but it’s possible that the incremental cost for adding it to AWS was cheaper.
- nevi-me 7y agoMy point is that those support functions' lack of understanding of realms outside of AWS shouldn't be the sole motivator for not using a technology. What happens if a company that uses Software A has good motivation to use B, but their support functions don't understand B? Aren't the support functions supposed to improve by seeking to understand B, even at the initial inconvenience of time and resources?
- mbreese 7y agoI certainly don’t disagree with you on principle. It’s just a bad example in this specific case because A is roughly equivalent to B in this case. Also, Amazon doesn’t have the same reputation as Google for killing products, so it’s a pretty safe bet. And AWS will be around for quite a long time. The financial stability of MongoDB (the company) isn’t as guaranteed. Maybe the parent’s company’s processes did work in this case.
- peteretep 7y agoMongoDB Inc wrote MongoDB, which is a major black mark against them.
- nailer 7y agoI actually use MongoDB Atlas for the same app now, because my usage fits in the free tier.
- rad_gruchalski 7y agohttps://aws.amazon.com/documentdb/pricing/ https://aws.amazon.com/documentdb/pricing/ At $0.277 it’s $19.94 for 72 hours.
- cj 7y agoI spend somewhere around $30-40k / yr on AWS (EC2) for a 3 member replica set. I evaluated DocumentDB and price wasn’t the issue (at our scale, the price is OK). Main blocker is that it’s locked at Mongo 3.4 API compatibility, which is several major versions behind. But worse, their implementation of the 3.4 API is incomplete, so while they advertise “Mongo Compatible”, it really isn’t a drop in replacement.
- farisjarrah 7y agoGoogle Cloud's managed SQL seems to have an option where the instance spins down automagically when its not in use.
- threeseed 7y agoSuper expensive and orders of magnitude slower in some cases. As much as I love a managed service this was a very disappointing effort from AWS.