Aspire is both a framework and a complete end-to-end content ingestion and content processing system.
Typically, Aspire is used as an end-to-end system for acquiring content, processing it, and publishing it to be indexed by search engines:
All of this is can be done within a single Aspire node (running on a single JVM) or across a cluster of machines cooperatively working together.
Note that Aspire components are only available for customers who purchase a connector license. See Aspire Product Categories for more information.
If you want to use the Aspire strictly as a component and pipeline processing machine, we recommend you use the framework.
If you want to use the connectors and publishers, we recommend that you run the Getting Started Tutorial.
Use the following to help distinguish between what you can do with Aspire from a connector and content processing point of view versus using Aspire as a developer framework.
Think of the following when entering this landscape!
A content source is a connector applied to a specific database, server, or source of data, configured to run a specific set of workflow tasks
No data no search
Aspire provides order where chaos reigns
A more Install & go product
Plug & play with repositories
Elastic, fault tolerant, distributable / clusterable
Some of what you will find: