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

MongoHQ releases SSD powered databases, autoscaling beta

blog.mongohq.com

Post reply on HN
Print view View original

11–20 of 28 posts

Re: MongoHQ releases SSD powered databases, autoscaling beta

#11

Post by tedchs »

nodesocket wrote: post #4

MongoHQ is awesome, and their control panel is hands down the best of the MongoDB PaaS, but their pricing is cost prohibitively expensive. For example, you can get a 2 core, 2GB memory, 20GB of SSD backed storage from DigitalOcean for $20 a month. So, buying three VM's from Digital Ocean for a replica set is a total of $60 a month. Essentially the same thing at MongoHQ is $500 a month. I completely understand that yo…

With a username like "nodesocket", I assume you are not their target audience as you are just as comfortable rolling your own and getting your own 10gen support contract.

Re: MongoHQ releases SSD powered databases, autoscaling beta

#12

Post by andypants »

tedchs wrote: post #9

I don't understand all the hate about MongoHQ's pricing. I run a Mongo replica set in production on bare EC2 and it works well, but there is a lot of reading/research involved in setting it up correctly and handling any Mongo issues that arise. Nothing stops you from doing that, and 10gen even provides a beautiful AWS CloudFormation template to make it easy to provision a replica set with EBS RAID. However if I were…

It's not the pricing I don't like, it's the relationship between pricing and storage space. I doubt when I go from a 0.5GB database to a 1GB database that they have to double their support team as well.

Heroku's postgres is just as (or more) expensive as mongohq/mongolab, but they don't limit storage at all (except at the dev tier plans).

Re: MongoHQ releases SSD powered databases, autoscaling beta

#13

Post by benmccann »

nodesocket wrote: post #4

MongoHQ is awesome, and their control panel is hands down the best of the MongoDB PaaS, but their pricing is cost prohibitively expensive. For example, you can get a 2 core, 2GB memory, 20GB of SSD backed storage from DigitalOcean for $20 a month. So, buying three VM's from Digital Ocean for a replica set is a total of $60 a month. Essentially the same thing at MongoHQ is $500 a month. I completely understand that yo…

This pricing is absolutely insane for anyone with a decent sized dataset. It'd cost about a quarter million dollars a year to store a terrabyte of data?!

Re: MongoHQ releases SSD powered databases, autoscaling beta

#14

Post by [deleted] »

nodesocket wrote: post #4

MongoHQ is awesome, and their control panel is hands down the best of the MongoDB PaaS, but their pricing is cost prohibitively expensive. For example, you can get a 2 core, 2GB memory, 20GB of SSD backed storage from DigitalOcean for $20 a month. So, buying three VM's from Digital Ocean for a replica set is a total of $60 a month. Essentially the same thing at MongoHQ is $500 a month. I completely understand that yo…

[deleted]

Re: MongoHQ releases SSD powered databases, autoscaling beta

#15

Post by benwyrosdick »

ig1 wrote: post #6

As far as I can tell they don't offer either SSL or SSH tunnelling, so there's no way you can securely connect to the database remotely. Without those you're sending your password and data unencrypted over a public network. By default Mongo uses MD5 for password hashing (with username as seed) so it's not secure to use it over a public network. (if your server is co-located on the same network as MongoHQ then you can…

We do offer an SSL option if you email support@mongohq.com

Re: MongoHQ releases SSD powered databases, autoscaling beta

#16

Post by lnanek2 »

andypants wrote: post #12
tedchs wrote: post #9

I don't understand all the hate about MongoHQ's pricing. I run a Mongo replica set in production on bare EC2 and it works well, but there is a lot of reading/research involved in setting it up correctly and handling any Mongo issues that arise. Nothing stops you from doing that, and 10gen even provides a beautiful AWS CloudFormation template to make it easy to provision a replica set with EBS RAID. However if I were…

It's not the pricing I don't like, it's the relationship between pricing and storage space. I doubt when I go from a 0.5GB database to a 1GB database that they have to double their support team as well. Heroku's postgres is just as (or more) expensive as mongohq/mongolab, but they don't limit storage at all (except at the dev tier plans).

Agreed. I have to do things like store large things in Amazon S3 when I'd really rather just stick it in GridFS. The pricing is just way to high to do anything else.

Re: MongoHQ releases SSD powered databases, autoscaling beta

#17

Post by nodesocket »

tedchs wrote: post #11
nodesocket wrote: post #4

MongoHQ is awesome, and their control panel is hands down the best of the MongoDB PaaS, but their pricing is cost prohibitively expensive. For example, you can get a 2 core, 2GB memory, 20GB of SSD backed storage from DigitalOcean for $20 a month. So, buying three VM's from Digital Ocean for a replica set is a total of $60 a month. Essentially the same thing at MongoHQ is $500 a month. I completely understand that yo…

With a username like "nodesocket", I assume you are not their target audience as you are just as comfortable rolling your own and getting your own 10gen support contract.

Actually I've used MongoHQ as well as MongoLab for development, but for http://commando.io it made sense to just purchase three virtual machines on Softlayer and setup MongoDB. Backups we quite easy as well, a few hours later we had a working bash script which stored backups locally, and well as synced them to S3.

Re: MongoHQ releases SSD powered databases, autoscaling beta

#18

Post by mrkurt »

andypants wrote: post #12
tedchs wrote: post #9

I don't understand all the hate about MongoHQ's pricing. I run a Mongo replica set in production on bare EC2 and it works well, but there is a lot of reading/research involved in setting it up correctly and handling any Mongo issues that arise. Nothing stops you from doing that, and 10gen even provides a beautiful AWS CloudFormation template to make it easy to provision a replica set with EBS RAID. However if I were…

It's not the pricing I don't like, it's the relationship between pricing and storage space. I doubt when I go from a 0.5GB database to a 1GB database that they have to double their support team as well. Heroku's postgres is just as (or more) expensive as mongohq/mongolab, but they don't limit storage at all (except at the dev tier plans).

Database storage space correlates pretty well to the management complexity, at least with our customer base.

Offering unlimited storage on a DB is somewhat disingenuous, there are effective resource limits that matter long before disk space and those (RAM/IO capacity) are the things that cost actual money.

Re: MongoHQ releases SSD powered databases, autoscaling beta

#19

Post by mrkurt »

nodesocket wrote: post #4

MongoHQ is awesome, and their control panel is hands down the best of the MongoDB PaaS, but their pricing is cost prohibitively expensive. For example, you can get a 2 core, 2GB memory, 20GB of SSD backed storage from DigitalOcean for $20 a month. So, buying three VM's from Digital Ocean for a replica set is a total of $60 a month. Essentially the same thing at MongoHQ is $500 a month. I completely understand that yo…

(I'm one of the MongoHQ founders)

It's less about the hardware and more about the DBA service. Most companies shouldn't be spending engineering time setting up DBs and don't have the expertise to run them when they're "catastrophically successful". We do, know what the watch for, and have on call DBAs that respond to issues within about 10 minutes, 24x7.

Re: MongoHQ releases SSD powered databases, autoscaling beta

#20

Post by mrkurt »

fiatmoney wrote: post #8

My impression has been that Mongo has great performance as long as your working set is totally in RAM, after which it craters (due to the use of MMAP'd files as the core storage engine and relying on the OS's paging algos). To what extent is this true on SSDs? Can you get away with a higher working-set-to-RAM ratio?

We've generally found that 1GB of RAM per 10GB of data is best for common Mongo setups. SSDs make a huge impact on the to-disk performance, which does help with the working set.

SSDs also help with writes and can help mitigate the infamous global write lock problems in Mongo.

Post reply on HN