Comment by binarymax
4 years ago
Elastic spends so much time and effort on making sure that their search is performant (and they are not shy about deprecating and removing features that are slow). I think this is where Elastic will continue to shine. It's one thing to add features, it's another to make it so they work well and make sure the integrating product team doesn't shoot themselves in the foot.
What may hurt them though, is the number of customers that currently feel things are currently "good enough". I don't know what their sales engagement looks like, so I'm not sure if this will really hurt them or not.
Perhaps! My money is on Elastic including an approximate nearest neighbor search in 8.0 which uses the new HNSW feature in Lucene 9, which is going to be hard to do in a distributed capacity and will be a significant feature if they can pull it off.
PS - I've never seen gitsense before and it's really cool. I especially like the focus quadrant!
Since search is your domain expertise, I'll take your word for it :-)
As for GitSense, checkout the impact section and sort contributors by "First Commit". With this, you'll get a very good idea of the developer's expertise level.
I agree, I trust there will be value for some in openSearch not using SSPL and value for others in Elastic's performant/scaleable tendencies.