Live data from Hacker News

Amazon CloudSearch - Start Searching in One Hour for Less Than $100 / Month

aws.typepad.com

41–50 of 91 posts

Re: Amazon CloudSearch - Start Searching in One Hour for Less Than $100 / Month

#42
post #31
post #2

You know this doesn't seem like a bad deal though $100/mo might be high for someone just starting out. Right now my options for search are: Full text SQL search Apache Solr or something similar Google Search Appliance Custom search Google free search on your site Yay for search as a service.

And if you want a hassle free scalable search service with automatic sharding/scaling, a lucene underpinning and a nice REST API: Elasticsearch

And if you want an actually good search product there is always SphinxSearch.

Re: Amazon CloudSearch - Start Searching in One Hour for Less Than $100 / Month

#43
post #17

interesting, I will check out for sure. Any plans for EU release? I am very interested in the facet-search functionality, anybody know if there is sort options on the returned facet's ? Most search engines just sort facets by number of hits.

You can sort facets in your application, not sure why you'd want the search engine to sort them, doesn't seem like a feature that belongs to the "back-end" search engine.

Say a query returns a million results, it makes much more sense to sort them on the search server and return the top 10 than to transfer them all to the application server and sort them there. Another use case is a custom ranking function which boosts the score of newer documents.

Re: Amazon CloudSearch - Start Searching in One Hour for Less Than $100 / Month

#45

Does this literally kill the Search as service provides like IndexTank, Unbxd etc.? It becomes a really tough market with AWS doing the same (~very similar) service.

I'm sure it won't "literally" kill anyone.

Re: Amazon CloudSearch - Start Searching in One Hour for Less Than $100 / Month

#46
post #42
post #31

Earlier quoted context omitted.

And if you want a hassle free scalable search service with automatic sharding/scaling, a lucene underpinning and a nice REST API: Elasticsearch

And if you want an actually good search product there is always SphinxSearch.

Why wouldn't you consider ElasticSearch to be an "actually good search product" ?

Re: Amazon CloudSearch - Start Searching in One Hour for Less Than $100 / Month

#47
Very interesting. I have a project that I'm about to start which is going to have an index of 4 million plus data records where I need high performance faceted search. I was exploring using Solr but may now give this a look as I'm planning on putting the app on EC2. Are there any technical details/tutorials on how their facets are configured?

Re: Amazon CloudSearch - Start Searching in One Hour for Less Than $100 / Month

#48
post #42
post #31

Earlier quoted context omitted.

And if you want a hassle free scalable search service with automatic sharding/scaling, a lucene underpinning and a nice REST API: Elasticsearch

And if you want an actually good search product there is always SphinxSearch.

Why the bashing on Elasticsearch? We are using it to index log files; we have over 275 million documents in our index and performance has been pretty impressive.

Re: Amazon CloudSearch - Start Searching in One Hour for Less Than $100 / Month

#49

They claim to support realtime indexing. I wonder what they really mean by that and how it impacts performance. SOLR is a great piece of software, I start using it 5 years ago and more recently implemented a near realtime indexing(publishing) integration but I always had to make some kind trade off between high performance and near "realtime indexing"

It says "near-real time", which is really just a synonym for "fast".

Re: Amazon CloudSearch - Start Searching in One Hour for Less Than $100 / Month

#50
post #42
post #31

Earlier quoted context omitted.

And if you want a hassle free scalable search service with automatic sharding/scaling, a lucene underpinning and a nice REST API: Elasticsearch

And if you want an actually good search product there is always SphinxSearch.

Last I checked, Sphinx had a huge design flaw in that it indexed directly from an SQL database. In other words, your Sphinx configuration not only needs to have read access to the database, it needs to contain the required SQL queries.

This tightly couples Sphinx to your application and your schema, and creates serious issues for your ops team since every app change potentially needs to modify the Sphinx config. It gets particularly hairy when you want to host multiple applications using a single Sphinx daemon.

We started out with Sphinx for our apps but quickly discarded it in favour of ElasticSearch, a much more elegant and orthogonal piece of software.

Post reply on HN