3 ms·
We've been looking at doing managed because we use ES for some projects. But at they're always running on the same server as the application. And we have nobody
by ClikeX 6y ago
We've been looking at doing managed because we use ES for some projects. But at they're always running on the same server as the application. And we have nobody with the knowledge or ambition to maintain it.
But reading these comments I get wary of doing it that way.
- vosper 6y agoI’m sure it depends what you’re doing - our cluster is medium-largeish, I’d guess (wish there was more info on the clusters that are out there!). Several hundred big EC2 instances, all NVMe, billions of documents, indexes in the terabytes, high update rate in addition to inserts. It requires fairly active management and optimization. We might just be outside of the sweet spot for the AWS offering.
- ClikeX 6y agoIf that is medium-largish, then I'd probably be more than fine within the use-case of my current customers.
- ignoramous 6y ago> Several hundred big EC2 instances, all NVMe, billions of documents, indexes in the terabytes, high update rate in addition to inserts. It requires fairly active management and optimization. AWS Elasticsearch may not be for power users but they did announce Petabyte and Ultrawarm for über scale clusters in run up to last year's re:Invent: https://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/ultrawarm.html https://docs.aws.amazon.com/elasticsearch-service/latest/dev... and https://aws.amazon.com/blogs/database/run-a-petabyte-scale-cluster-in-amazon-elasticsearch-service/ https://aws.amazon.com/blogs/database/run-a-petabyte-scale-c...