Here’s a question we hear a lot:

If Lucidworks Enterprise is built on Solr, how do you know which one to use when for your own circumstances?

We thought you might find it useful to take a closer look at this question before you try building a search application yourself. We think you’ll find there’s a lot they have in common, some advantages to using Lucidworks Enterprise (which is why we think it’s pretty exciting in the first place). Most importantly, we want you to think about how you build your search application. If you’re using Solr today, or even if you’re not, this article should help you in considering how Lucidworks Enterprise can help you make search application development more accessible, how you can build better faster Solr applications, and of course, keep the cost of growth lower.

If you’re building a search app, you generally go through these steps:

  1. Define your indexed content
  2. Define your data
  3. Define user/data domains
  4. Index your data
  5. Build your application (including facets, autocomplete, etc.)
    Issue queries through the built-in query interface
  6. Keep your indexes updated
  7. Control access
  8. Monitor the system

We’ll compare the following technologies you can use for this:

  • Straight Solr: In this case, you’ve got the engine and all of the flexibility that provides, but there’s a lot you will need to do yourself. You may get more fine-grained control, but it comes at a price for ongoing maintenance, and might require higher-skilled resources to invest their attention in more mundane work.
  • Lucidworks Enterprise web-based user interface: The LWE UI provides easy ways to accomplish common tasks, but there are times you might need to go beyond that to the ReST API. A UI is not scriptable, but it’s easy to point and click, particularly if some of your administrators are not comfortable with scripting.
  • Lucidworks Enterprise ReST API: All of the capabilities Lucidworks Enterprise offers are also available via ReST API. Simply put, the ReST API enables you to accomplish tasks programmatically using HTTP calls, with some scripting; the scripting, in turn, enables creation of repeatable processes and automation.

Read the full article here.