Architecture of an Enterprise Search Application

For those of you that landed directly on this page, I am working on a series of post that help people “Get Started with Enterprise Search using Apache Solr”. In this post I cover one specific module. If interested in watching the course please click here: http://pluralsight.com/training/courses/TableOfContents?courseName=enterprise-search-using-apache-solr . Click here to get to the starting point: https://www.xaviermorera.com/2014/06/getting-started-with-enterprise-search-using-apache-solr/ In the second module I start by trying to make my point on how

• Beauty is in the eye of the beholder
• Users usually don’t care about the application
• They care about getting accurate and fast results.

Users don’t care about the how, engineers care about the how. The people that use it don’t. and that’s what counts! Then I focus for a few minutes on explaining architecture from two points of view:

• Where, architecturally speaking, within an application does the search engine fit in

• Solr’s architecture

The third section of this module explains what makes Solr move and shake, mainly the search engine underneath: Lucene. And finally I explain to you the parts of a search application. This part may be a bit subjective depending on who looks at it, but most principles apply across the board. If you are interested on viewing this module you can start here:  enterprise-search-apache-solr-m2 Here is the table of contents:

Architecture of an Enterprise Search Application		00:12:32
Architecture		00:30
Beauty and Simplicity		01:20
Architectural Review		05:06
Lucene the Search Engine		02:24
Search Applications		02:13
Takeaway		00:57

You can also go back to the main page of this series by clicking here: https://www.xaviermorera.com/2014/06/getting-started-with-enterprise-search-using-apache-solr/