by softwaredoug on 6/5/25, 6:37 PM with 24 comments
by sh34r on 6/6/25, 7:07 AM
Improving your simple website's search function will take days or weeks, not hours. If you make your own search engine, it's almost guaranteed to be worse than ElasticSearch.
by nchmy on 6/6/25, 12:04 PM
Much easier to deal with and faster than elastic
by fucalost on 6/6/25, 5:59 PM
Sure it’s computationally expensive, inefficient even, but for many use-cases it just works.
I’d add that for production deployments, AWS has developed a new instance family that enables OpenSearch data to be stored on S3 [1], bringing significant cost savings.
[1] https://docs.aws.amazon.com/opensearch-service/latest/develo...
by intalentive on 6/7/25, 4:43 PM
Also you can get some cool behavior out of representing a corpus as a competitive network that reverberates, where a query yields an “impulse response”.
by amai on 6/6/25, 7:39 PM
by 0xB0UNCE00 on 6/6/25, 3:51 PM
by Alifatisk on 6/6/25, 9:51 AM
by niazangels on 6/6/25, 2:38 AM
by neuroelectron on 6/6/25, 2:56 AM
by stuaxo on 6/6/25, 11:06 AM
(To be fair, I've only worked on projects that use ES where it is entirely unnessacary).