FUSE doesn’t technically compete with the Lucene, Elastic Search, or Solr platforms. In fact, FUSE’s technology stack uses a licensed version of Elastic Search.
Sometimes when we talk to organizations or partners about FUSE they’ll tell us something like “oh, we don’t need FUSE - we’re already using Solr for search” or “we just bought Elastic - but thanks!”
FUSE is all about federated search - indexing content from multiple platforms and unifying it in one set of search results. This requires development and maintaining of several components for an organization to accomplish independently using Lucene, Elastic Search, or Solr. In other words, FUSE is made up of more than the search technology platform. It’s:
Connector Development. These are the chunks of code that access the various APIs of services that house your content. We also sometimes call these importers. We have many frequently used connectors ready to deploy but connect to new sources all of the time.
Connector Monitoring and Maintenance. Let’s say one of the third party services updates their API — we handle re-connecting to the content source for no additional fees. We also make sure your users never see an outage: searching will continue as normal using a prior index of the content until the connection can be repaired.
Improvements. Since FUSE is software as a service (SaaS), we’re improving All. Of. The. Time. Check out our roadmap for forthcoming innovations. Most of the improvements we make to FUSE get pushed out to all FUSE clients — you don’t have to lift a finger or even ask. On occasion, a new feature or improvement is added that’s considered premium for which current FUSE clients are typically offered a very reduced fee upgrade.
Hosting. FUSE runs from Amazon Web Services (AWS) - we store your index
Integration into your Site. sadfafsaf