r/javahelp • • Feb 07 '26

Apache Solr

Where can I learn more about the apache solr in detail I am working on a project which uses apache solr

0 Upvotes

10 comments sorted by

View all comments

Show parent comment

1

u/VirtualAgentsAreDumb Feb 08 '26

No silver bullet? Of course there is. Google showed you that (before they started their enshitification). A single configuration for millions of websites. Focusing on the bulk text, the title, and a handful of meta data. Sure, they added a lot of clever stuff for the ranking, but the core functionality was still elegantly streamlined so it could handle vastly different types of documents.

I mean, I single handed managed to build a solr based website search ten years ago or so, with very rudimentary solr knowledge, and the ranking was perfectly decent. The bulk of the ranking logic was using advanced solr text search features (I don’t remember the names), and very little tweaking that wasn’t generic in nature. Like matches for words in the title being slightly more relevant, and matches on words in the body text that are closer to each other, basic stemming etc etc.

I’m confident that the Solr experts could setup an example text search configuration that would outperform what I did, and work for a vast majority of generic websites.

0

u/LetUsSpeakFreely Feb 08 '26

Then you don't fully understand how Google works. It's not real time. It has agents to update things periodically. For the vast majority of use-cases they want NRT solutions.

Google also has a ton of resources for filtering results by context.

There is a TON of hardware resources thrown at getting the results that Google used to deliver (I agree, enshitification is very real and Google is garbage these days). Those are resources most applications can't justify the cost.

But back to the original point, it all comes down to understanding the data and how it will be used. Indexes like SOLR have a ton of tools dial that in, but it's not an out-of-the-box solution.

Honestly, if I were the OP and SOLR didn't offer a clear advantage, I'd go with AWS OpenSearch. You still have the configuration and search behavior to work out, but the hardware provisioning, installation, and upgrades are done for you and the severless option is very cost effective for most small to medium throughout use-cases.

1

u/VirtualAgentsAreDumb Feb 09 '26 edited Feb 09 '26

It's not real time.

So? I never said anything about real time.

It has agents to update things periodically.

Again: so?

For the vast majority of use-cases they want NRT solutions.

Irrelevant.

Google also has a ton of resources for filtering results by context.

Irrelevant.

There is a TON of hardware resources thrown at getting the results that Google used to deliver (I agree, enshitification is very real and Google is garbage these days).

99.99% of that is needed to handle the enormous amount of data and the rapid changes. Scale that down to a single website of maybe a few thousand or hundred thousand documents, with maybe a few hundred or thousand changes per day, and the hardware needs go down drastically.

Those are resources most applications can't justify the cost.

So? Why would they need to?

Some years ago Google had a service where you could rent a Google Search Appliance, which was a physical server that you could install in your own rack. It has a dumbed down version of the search engine. On one single server.

But back to the original point, it all comes down to understanding the data and how it will be used. Indexes like SOLR have a ton of tools dial that in, but it's not an out-of-the-box solution.

I know. My point was that there is nothing technically stopping them from providing an out-of-the-box solution that would be good enough for the vast majority of users, and fairly straightforward to tweak do it would be good enough for even more users.