3 ms·
HN skews very anti-mongo, but it can be a good fit for certain apps -- I would stick with what you know until you think you've outgrown what you can do without
by mattbillenstein 9y ago
HN skews very anti-mongo, but it can be a good fit for certain apps -- I would stick with what you know until you think you've outgrown what you can do without sharding. I'd probably never shard mongo, but if you can vertically scale it for awhile, I'd do that.
If you're on ec2, the i3 instances have very fast nvme instance storage at a reasonable (cloud) price.
- rubyfan 9y agoI agree with the sentiment. Don’t refactor unless it’s failing you. Just be mindful you might refactor someday and backup your data.
- nikkwong 9y agoSounds good to me. I looked into sharding in the past but never took the leap as it added tons of complexity. Thanks so much!
- gerenuk 9y agoWhat would you suggest instead of mongodb for large scale production db? Our DB size is growing on daily basis and currently near to 200GB on a dedicated machine.
- brianwawok 9y agoPostgres or cassandra depending on scale and use case.
- mattbillenstein 9y agoIt depends -- if it's analytics, I'd look to ship it to a hosted system (I like BigQuery). If it's not, you might be able to scale up to terabyte or two before sharding; then maybe cassandra or one of the sharded postgres things (Citus, postgres-xl?)? I haven't had that problem in awhile.
- richardknop 9y agoDepends on data. If it's time series data then I would use time series database like InfluxDB. But again you might be fine even with Postgres or Mongo. Depends on structure and type of data.