Query it however your application needs
Different processes and screens in your application need different things from the same data. LipiCore Engine answers all of it through one API.
Search
- Full text search upon defined fields with typo tolerance
- Weight fields and boosted search
- Typeahead suggestions as the user types
- Spell correction using your own data as dictionary
Listings
- Filter on any indexed field
- Multiple fields sorting with bi-direction
- Standard pagination structure
Facets
- Field facets - counts per value
- Stat facets - sum, average, min, max, median
- Range facets - numeric, currency and date buckets
- Nested facets - use any of the above facets one within another Learn more
A facet inside another facet. Ask for revenue by region, and within each region get the same breakdown by product category, each level carrying its own counts and totals.
Any facet type can nest inside any other, to whatever depth the screen needs.
Alongside your systems, not in front of them
Your ERP, CRM and production databases keep doing what they do today. LipiCore Engine sits alongside them with an indexed copy of the data you send it.
Data in LipiCore Engine is organized into collections, with each collection maintaining its own index and update schedule.
Built on Apache Solr
LipiCore Engine is built on Apache Solr, a proven open-source search and indexing technology designed for large volumes of data and complex queries.
Your applications do not need to interact with Solr directly. LipiCore Engine handles the indexing, mapping and query translation, and exposes REST APIs for your applications to use instead.
Solr is the indexing foundation. LipiCore Engine is what your applications talk to.
Questions engineering teams ask
Databases are built to store and manage data. As application queries become more complex, such as searching across multiple fields, applying filters with counts, or calculating totals on filtered results, they can put heavy load on the production database. LipiCore Engine keeps an indexed copy optimized for those queries, so your applications get faster access without competing with your transactional workloads.
No. Your database remains the source of truth, and your applications keep their existing architecture. You can route specific screens or data-heavy experiences, typically the slow ones, through LipiCore Engine for faster access. You only integrate the parts that benefit from it.
Use LipiCore Engine wherever your applications need fast access to large volumes of records.
This can include catalog and product search, internal consoles searching millions of rows, listing screens with filters, sorting and pagination, and reporting screens that need totals without querying your production database.
You can use it for specific screens or workflows without changing the rest of your application.
Your applications call LipiCore Engine through secure REST APIs. Send a request naming the collection and what you need, and LipiCore Engine can return records, counts, ranges and totals together, so a full search screen can often be powered by a single API call.
Your systems can push records through the API, or LipiCore Engine can pull data from your database on a schedule. Each collection can have its own schedule, from hourly to weekly, and can run a full import or bring in only new and changed records.
LipiCore Engine runs entirely inside your infrastructure, whether on-premise or in your private cloud. Your data stays within your environment. Nothing is hosted on LipiCore servers.
We deploy LipiCore Engine inside your infrastructure, connect your data source, configure the collections you need and import the data. Your development team can then connect specific application screens or workflows to LipiCore Engine through its REST APIs.
Access the LipiCore Engine
Get in touch with our team to see how LipiCore Engine can improve the performance of your applications.