3 ms·
The very, very poor tradesman blames the tool. > However, so many fundamental features are either disabled or missing in AWS Elasticsearch that it’s exacerbate
by tus88 7y ago
The very, very poor tradesman blames the tool.
> However, so many fundamental features are either disabled or missing in AWS Elasticsearch that it’s exacerbated almost every other issue we face.
No, your choice to use AWS Elastic Search is compounding all the other poor decisions you have already made (and admitted to). This is just another one of them. Petabyte scale ElastcSearch clusters are approaching edge case usage scenarios, and one most people would expect an average SAAS solution may not be optimized for.
You could have spun up - and managed - your own cluster on EC2 but instead decided to make bad decisions probably without any research or beta testing, got badly burned as a result, and are now trying to unload your sour grapes on to the interwebs.
- fiddlerwoaroof 7y agoThis sort of experience report is extremely valuable for people evaluating AWS services or trying to make a case to switch to a self-managed service.
- outworlder 7y ago> The very, very poor tradesman blames the tool. But a good tradesman will not use inferior tools.
- tus88 7y agoA good tradesman uses the right tool for the task at hand.
- deleted 7y ago[deleted]