Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Top Three Drivers of Solr Adoption

DZone's Guide to

Top Three Drivers of Solr Adoption

· Java Zone ·
Free Resource

Get the Edge with a Professional Java IDE. 30-day free trial.

We’ve been talking to our customers to understand why they are adopting Solr. Is it because it’s a great product from the Apache Software Foundation? Is it because Lucene has a cute naming story? Is it because of Solr’s compelling feature set, ease of use, and great admin interface?

Unfortunately, it’s none of those reasons. The top three reasons for adopting Solr are:

  • Vendor Fatigue. Companies are tired of being tied up in complex and expensive licensing contracts, per document pricing schemes, and opaque service agreements. This Dilbert comic I saw in the paper today struck very closely:

    Dilbert.com

    This is why our basic services agreement is a 1 pager!
  • Flexibility. We’ve worked with a number of clients who’ve used Google Search Appliance and Google Custom Search because they were so gosh darn simple to setup. They subsequently moved to Solr because they either ran into the limitations for indexing information or presenting a rich search user experience with those solutions. With Solr, you can integrate with any datasource, and display your search results in whatever format you need. The more “seamless” you want your search experience to be with your site, the better Solr looks.
  • Stability. As much as I love Lucene, it’s a very complex beast. And many organizations have developed their own search engines on top of Lucene that have become expensive to manage, and don’t offer the features that Solr does. We’re going to be busy for a long time helping companies move from pure Lucene based search to Solr!

Get the Java IDE that understands code & makes developing enjoyable. Level up your code with IntelliJ IDEA. Download the free trial.

Topics:

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}