Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I'm not sure what the author was referring to, but in our stack ES is the only non-serverless tech we have to work with. I know there's a lot of hate in HN around serverless for many reasons but for us for several years, we've been able to scale without any worry of our systems being affected performance-wise (I know this won't last forever).

ES is not this way, we have to manage our nodes ourselves and figure out "that one node is failing, why?" type questions. I hear they're working on a serverless version, but honestly, I think we will be leaving ES before that happens.



Elastic’s serverless offering went GA recently: https://www.elastic.co/elasticsearch/serverless


It's still in technical preview.


> that one node is failing, why

We have a similar experience except we’re using AWS’ version, so any inquiry as to what happened ends with support saying “maybe if you upgrade your nodes this won’t happen again? idk”


And that's why we pay AWS the big bucks.


What are you considering replacing it with for full-text search?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: