Sonic

Sonic — fast, lightweight search backend, no indexing overhead.

SearchSimple

Stack Components

EngineSonic 1.x

Why

100MB binary, Rust-powered, key-value search, no full text index. Meilisearch and Typesense emerged as open-source Algolia alternatives, 5-10x cheaper at scale.

Algolia handles 1.5B+ searches/month with sub-50ms latency via its MRR ranking algorithm.

When

Use for autocomplete and simple search. Avoid for complex queries.

How

1. Run sonic-server 2. Push key-value pairs 3. Query with suggest/search 4. Use in app 5. Add environment configuration — cp .env.example .env && edit values 6. Run tests — npm test or pnpm test to verify setup 7. Deploy — git push to trigger CI/CD or manual deploy

Example

// Push: PUSH collection bucket "key" "text" // Search: SEARCH collection bucket "query" // Sonic — usage example import { Sonic } from "search2-sonic"; const result = await sonic({ input: "data" }); console.log(result);

Common Problems

⚠No full-text search — use for autocomplete only
⚠Limited query language — use Meilisearch for complex
⚠Configuration drift between environments — use infrastructure-as-code (Terraform/Pulumi) to keep dev/staging/prod identical

Best Practices

✓Use suggest for autocomplete
✓Batch pushes for throughput
✓Set up health checks and graceful shutdown — handle SIGTERM to drain in-flight requests before exit

FAQ

What is Sonic and what projects is it for?

Sonic — fast, lightweight search backend, no indexing overhead. It pairs layered technologies for end-to-end type safety and out-of-the-box deploys, fitting everything from MVPs to production SaaS.

How do I spin up a working demo with Sonic in 10 minutes?

Two steps: (1) Run sonic-server; (2) Push key-value pairs. Get the local dev server running, then wire one real data source to verify the end-to-end loop.

What is the most common pitfall with Sonic and how do I avoid it?

The most common pitfall is: No full-text search — use for autocomplete only. Avoid it by adding the matching checklist to your PR template and running type-check + lint + unit tests in CI — three gates before merge.

What are the best practices for Sonic?

Best practices for Sonic include: Use suggest for autocomplete; Batch pushes for throughput; Set up health checks and graceful shutdown — handle SIGTERM to drain in-flight requests before exit. The first one — "Use suggest for autocomplete" — should be set up at project init to avoid costly rework later.

When should I NOT choose Sonic?

Pick something else in three cases: (1) the team has zero experience with the core framework and the deadline is tight (learning-curve risk); (2) it's a pure content/marketing site (Astro is lighter); (3) you need very high throughput (>10k RPS) or strict-consistency microservices (Go/Rust). Sonic shines for mid-to-high complexity full-stack and API work — don't over-engineer simple static pages with it.