What to choose: Amazon CloudSearch or ElasticSearch on EC2?

Question

Ruby on Rails

Gentlemen, a serious question: should you choose Amazon CloudSearch for a Rails application when deploying to AWS OpsWorks, or will it be easy enough to manage the configuration and support of 1 or several ElasticSearch nodes on EC2 instances? There are many comparison criteria, I have already compiled a portrait of each of these engines for myself, but I'm interested in how "wooden" CloudSearch is in terms of unexpected plugs in configuration flexibility, data import. Because I have already encountered this in other Amazon products: if you want to configure it more conveniently for your solution, everything falls apart and fills you with tons of incomprehensible error messages (this was the case with Elastic Beanstalk).
Those. Is it worth messing around with manually configuring ElasticSearch due to the possible inflexibility of CloudSearch?

Answer 1

I will not sign here, I will say briefly. I would use ES.
1. We scale just a fairy tale
2. Although both will cope, but ES is much faster and will work faster for reports and by default already includes statistical data in any answer.
Well, even if both manage now, then suddenly such a moment will come that it is necessary to expand? It will probably be easier and cheaper to expand ES.
Still it is necessary to consider that ES though in a name search is all the same a database. It's just called that. And CS is a search index. I think it will generally not be possible to use it at some points as a database.

Answer 2

What are your search queries?
Already from them and it is necessary to repel.

Answer 3

You can use hosted ElasticSearch https://bonsai.io/ if you don't want to set up and maintain servers with it.