5 ms·
It looks like they wanted to run Mongo inside their own Amazon account- under their direct control. AWS could do that with Postgres while MongoDB couldn't.
by lykr0n 8y ago
It looks like they wanted to run Mongo inside their own Amazon account- under their direct control. AWS could do that with Postgres while MongoDB couldn't.
- flatiron 8y agothey talked about NTP. which to me means Mongo on EC2 maybe?
- lykr0n 8y agoThat's what I understood they were doing and they didn't want to do that anymore.
- wftglf 8y agoYep that's what we were doing, and the management software (OpsManager) was also running on EC2 instances. We messed up the VPC configuration so that NTP didn't work on some of the instances - which unsurprisingly broke authentication between OpsManager and the db instances
- scarface74 8y agoThat makes me sad. I would love for AWS to have a hosted Mongo solution or some type of NoSQL database besides DynamoDB. Do people use ElasticSearch as a primary data store? In my limited experience implementations don’t treat it as the source of truth.
- snuxoll 8y agoElasticSearch doesn’t have adequate data integrity to treat it as a primary data store for most use cases.
- jstarfish 8y agoYes, but it only works if absolute-goddamn-integrity is not a concern. We unfortunately inherited a cluster from someone who thought it would be appropriate as a SoT for forensic data, which causes me no end of grief.
- lykr0n 8y agoYou could do what they are doing here
- dhd415 8y agoElastic maintains a page documenting the current status of their "resiliency" efforts on Elasticsearch: https://www.elastic.co/guide/en/elasticsearch/resiliency/current/index.html https://www.elastic.co/guide/en/elasticsearch/resiliency/cur...
- h1d 8y agoWhat's wrong with running a EC2 instance with Mongo in it?
- lykr0n 8y agoNothing, but they outline their problems in the article