Amazon AWS CloudSearch Review

Text-based search API and geospatial searches are valuable but index cleanup can be painful


How has it helped my organization?

We were able to build the core search functionality using this product.

What is most valuable?

  • Document indexing
  • Text-based search API
  • Geospatial searches

What needs improvement?

Latlon data type only supports single value per document. All other types support multiple values. We faced issues with this because we had scenarios where, for each document, we needed to store multiple latlon values for different geographical locations.

For how long have I used the solution?

One to three years.

What do I think about the stability of the solution?

No issues with stability.

What do I think about the scalability of the solution?

Index cleanup is sometimes painful. No easy way to clean indexes or a bulk of documents. Full indexing or regeneration of entire indexes sometimes gets stuck. In one instance, we had to delete the entire index and re-create it.

Which solutions did we use previously?

This was the first implementation, we did not switch from any other product.

How was the initial setup?

No setup required, as it is on cloud.

What's my experience with pricing, setup cost, and licensing?

I was not involved with pricing and licensing, I was only involved in implementation.

Which other solutions did I evaluate?

I would suggest looking at Elasticsearch. I am currently using it and I feel it is more flexible and easy to use.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Add a Comment
Guest
Sign Up with Email