Why we chose Mongo + Hypertable 14 years ago
They're pictures of our office in Durham, NC.
HN user
They're pictures of our office in Durham, NC.
We're still on EC2, though we've learned to distribute servers across availability zones.
Its single-threaded nature for map/reduce is its biggest liability in my opintion. It will apparently be fixed in the next version (https://jira.mongodb.org/browse/SERVER-4258)
Right now, large map/reduce operations just bring the thing to its knees. So we just don't map/reduce with it. The query features are really quite nice, and we do the rest in hypertable.