sonic
🦔 Fast, lightweight & schema-less search backend. An alternative to Elasticsearch that runs on a few MBs of RAM.
What is sonic?
🦔 Fast, lightweight & schema-less search backend. An alternative to Elasticsearch that runs on a few MBs of RAM.
Overview of sonic
What it is
Sonic is a fast, lightweight and schema-less search backend. It ingests search texts and identifier tuples that can then be queried against in a microsecond's time. It is an alternative to Elasticsearch that runs on a few MBs of RAM. Sonic is an identifier index, not a document index; when queried, it returns IDs that can then be used to refer to the matched documents in an external database.
Key features
- Search terms are stored in collections, organized in buckets.
- Search results return object identifiers, not direct textual data.
- Search query typos are corrected if there are not enough exact-match results.
- Insert and remove items in the index while the server is running.
- Auto-complete any word in real-time via the suggest operation.
- Full Unicode compatibility on 80+ most spoken languages, with stop word removal.
- Simple protocol (Sonic Channel) for search, ingestion, and administration.
Use cases
Sonic can be used as a simple alternative to heavy search backends like Elasticsearch in some use-cases. It is used by Crisp to index half a billion objects on a low-cost cloud server. It is suitable for applications that need fast search and auto-completion without storing full documents.
Getting started
Install Sonic via Cargo:
cargo install sonic-server
After installation, ensure your $PATH is configured to source the Crates binaries, then run Sonic using the sonic command. For detailed configuration, see the repository README.
License and pricing
License: MPL-2.0. Pricing: open source (free).
Based on the project's public README and repository metadata.