Fuzzy Search Implementation for Web Applications

Fuzzy Search Implementation for Web Applications

A user types "наушниик" — empty result. 70% of those visitors leave for competitors. Fuzzy search fixes typos and returns relevant products. Over the years, we've implemented fuzzy search for more than 30 e-commerce and catalog projects. We choose the engine that fits your stack and load: pg_trgm, Meilisearch, or Elasticsearch. With proper tuning, conversion grows by 15–25%, and maintenance costs drop — our cases confirm this.

For example, for an online home appliance store, we reduced the rate of empty results from 25% to 3% by switching to Meilisearch. Conversion increased by 22%. Response time dropped from 200 ms to 4 ms. Order a pilot project — we'll test on your data for free.

What distance algorithms are used?

Levenshtein distance — the minimum number of insertions, deletions, and substitutions to change one string into another, described on Wikipedia. Damerau-Levenshtein distance adds transposition (swapping adjacent characters). For Russian, it's preferable: "наушники" → "наушинки" is one transposition instead of two operations. In practice, we use Damerau-Levenshtein. The choice affects quality: Damerau-Levenshtein yields 10% fewer misses for Russian queries.

PostgreSQL: pg_trgm

The pg_trgm extension works with trigrams and requires no external services. It's the simplest solution if your stack already includes PostgreSQL.

CREATE EXTENSION IF NOT EXISTS pg_trgm;
CREATE INDEX idx_products_title_trgm ON products USING GIN (title gin_trgm_ops);
CREATE INDEX idx_products_description_trgm ON products USING GIN (description gin_trgm_ops);

SET pg_trgm.similarity_threshold = 0.3;

SELECT id, title, similarity(title, 'наушниик') AS sim
FROM products
WHERE title % 'наушниик'
ORDER BY sim DESC
LIMIT 10;

-- Combine fuzzy with full-text search
SELECT p.id, p.title, p.price,
       greatest(similarity(p.title, 'беспродные наушники'),
                ts_rank(p.search_vector, plainto_tsquery('russian', 'беспродные наушники'))) AS relevance
FROM products p
WHERE p.title % 'беспродные наушники'
   OR p.search_vector @@ plainto_tsquery('russian', 'беспродные')
ORDER BY relevance DESC
LIMIT 20;

The % operator uses the GIN index. The similarity_threshold of 0.3 is liberal; 0.5 is strict. For short queries, choose the lower bound. In practice, we recommend starting at 0.3 and adjusting through A/B tests: raising the threshold to 0.5 reduces false positives but may miss some relevant results. Infrastructure savings with pg_trgm amount to up to 40% compared to external engines.

Meilisearch — Dedicated Fuzzy Engine

Meilisearch is written in Rust and supports typo tolerance out of the box. It's specifically designed for fast fuzzy search and requires little configuration.

import meilisearch

client = meilisearch.Client('http://localhost:7700', 'your-master-key')
index = client.index('products')

# Index settings
index.update_settings({
    'searchableAttributes': ['title', 'brand', 'description', 'tags'],
    'filterableAttributes': ['category_id', 'status', 'price', 'brand'],
    'sortableAttributes': ['price', 'created_at', 'popularity'],
    'rankingRules': ['words', 'typo', 'proximity', 'attribute', 'sort', 'exactness'],
    'typoTolerance': {
        'enabled': True,
        'minWordSizeForTypos': { 'oneTypo': 5, 'twoTypos': 9 },
        'disableOnWords': ['iPhone', 'iPad'],
        'disableOnAttributes': ['sku', 'barcode'],
    },
    'pagination': { 'maxTotalHits': 10000 },
})

# Batch indexing
batch_size = 1000
for i in range(0, len(documents), batch_size):
    batch = documents[i:i + batch_size]
    task = index.add_documents(batch)
    index.wait_for_task(task.task_uid)

{
  "hits": [
    {
      "id": 1234,
      "title": "Sony WH-1000XM5 wireless headphones",
      "_formatted": { "title": "Sony WH-1000XM5 wireless <mark>headphones</mark>" }
    }
  ],
  "query": "headphon es sony",
  "processingTimeMs": 4,
  "totalHits": 38,
  "page": 1,
  "hitsPerPage": 20
}

Meilisearch delivers average response times under 10 ms for catalogs up to 10 million records, which is 10x faster than pg_trgm on large volumes.

Elasticsearch: Fuzzy Query

If Elasticsearch is already in use, add fuzzy to a multi-match:

{
  "query": {
    "bool": {
      "should": [
        {
          "multi_match": {
            "query": "наушниик",
            "fields": ["title^3", "brand^2", "description"],
            "fuzziness": "AUTO",
            "prefix_length": 2,
            "max_expansions": 50
          }
        },
        {
          "match_phrase": {
            "title": {
              "query": "наушниик",
              "slop": 2
            }
          }
        }
      ]
    }
  }
}

prefix_length: 2 — exact match of the first two characters reduces false positives. Elasticsearch suits large volumes (10M+) and analytics integration, but requires more complex infrastructure.

Which engine to choose?

For startups, pg_trgm is optimal — minimal deployment cost. If you expect growth, plan migration to Meilisearch. For enterprise projects with analytics, Elasticsearch.

Why typo tolerance tuning is critical?

Each parameter affects quality: too liberal thresholds produce noise, too strict miss typos. In practice, we use:

Fine-tuning yields a 15–25% conversion lift based on our measurements across 30+ projects. Post-launch rework savings amount to up to 30% of team time.

Process

Analytics — audit current search, collect typo statistics. Engine selection — pg_trgm, Meilisearch, or Elasticsearch for your stack. Integration — configure indexes, settings, API. Testing — A/B test with real queries, adjust thresholds. Deployment — monitor and support.

Timelines

pg_trgm (extension, indexes, queries, tuning threshold): 1 day. Meilisearch (deploy, configure, sync, API): 2–3 days. Fuzzy in existing Elasticsearch: 1 day.

What's included

Index configuration and typo type settings. Integration via REST API or SDK. Operations documentation. Warranty — we fix bugs within 2 weeks.

We'll assess implementing fuzzy search for your project. Get a consultation — contact us. We'll help choose the optimal solution and configure it for your stack.

Backend Development Services: Laravel, Node.js, Go, Django, PostgreSQL

On a production server at 3:14 AM, the Laravel Jobs queue stopped processing. 40,000 unprocessed jobs in Redis. Cause: worker crashed due to a memory leak in one of the Jobs (leak via a static variable in an Eloquent observer), supervisor didn't restart it because of misconfigured stopwaitsecs. This is not a hypothetical scenario — it's Tuesday. We analyzed such an incident on a project with 500 RPS load: diagnosis took 4 hours, fix — 20 minutes. So you don't lose money on downtime, we offer backend development services with a focus on production-grade reliability. We'll assess your project in 2 days.

Backend is what works when no one is watching. Or doesn't work. We guarantee you'll have the first option.

How do we ensure production-grade reliability from day one?

What we do correctly from day one

Service Layer over Fat Controllers. Controller receives HTTP request, validates it via Form Request, passes data to Service, returns response. Business logic in Service, not Controller. This sounds trivial, but most legacy projects have controllers with 500 lines and SQL queries inside.

Repository Pattern we use cautiously. If you just wrap Model::where(...) in a repository method — that's boilerplate without benefit. Repository is justified when: you need to abstract from the data source (DB + cache + external API) or when query logic is complex enough to isolate.

Jobs, Events, Listeners. Everything that can be async — make async. Sending email, PDF generation, external API sync, aggregate recalculation — into Queue. Laravel Horizon for queue monitoring in Redis: see throughput, failed jobs, processing time per queue.

How Octane handles high load

Laravel Octane with RoadRunner or Swoole keeps the app in memory between requests — removes bootstrap overhead (config loading, class autoloading) on each HTTP request. Gain: 3–8x on synthetic benchmarks, 2–4x on real applications. Important: no state between requests in static variables — that leads to exactly the incidents from the beginning. We use this in projects with >1000 RPS.

What to do about N+1 queries

N+1 is the most common cause of slow pages in Laravel apps. Standard story: page worked fine on dev with 10 records, on production with 10,000 — 8-second load.

Laravel Debugbar in dev environment shows the number of queries per page. More than 20 queries per page — signal for audit.

Model::preventLazyLoading(! app()->isProduction());

Telescope for profiling in staging: logs all queries, jobs, mail, notifications with time detail. Numbers: after implementing eager loading, page load time drops from 8s to 0.3s — 27 times faster.

PostgreSQL: indexes that are actually needed

PostgreSQL 14+ is the primary DB on all projects. We use PgBouncer + PostgreSQL combination. 10+ years experience, more than 50 backend projects, 5 years on the market.

How PostgreSQL helps avoid slow queries

Composite indexes for frequent WHERE + ORDER BY. If you have WHERE user_id = ? AND status = ? ORDER BY created_at DESC — you need (user_id, status, created_at DESC). A separate index on (user_id) doesn't help much with sorting.

Partial indexes. If 95% of queries go with WHERE status = 'active':

CREATE INDEX idx_orders_active ON orders (created_at DESC)
WHERE status = 'active';

The index is small, fast, covers the main load.

GIN indexes for JSONB and arrays. @> operator without GIN index — seq scan. With index — fast even on millions of rows.

GIN for full-text search. to_tsvector + GIN instead of LIKE '%query%'. LIKE without index is always seq scan. With pg_trgm extension and gin_trgm_ops — supports LIKE with index, useful for CRM search by partial match.

Connection pooling: why it's more important than it seems

Rails, Laravel, Django open a new connection to PostgreSQL for each PHP/Python process. With 100 workers — 100 connections. PostgreSQL starts degrading from 200–300 active connections — overhead on connection management becomes significant.

PgBouncer — connection pooler in front of PostgreSQL. Transaction pooling mode: connection to PostgreSQL is occupied only during a transaction, returned to pool between requests. 1000 application workers → 20–50 actual connections to PostgreSQL. This reduces latency by 40% and hosting costs by 30%.

Node.js with Fastify: when it's better than Laravel

Node.js is justified for:

• Realtime: WebSocket servers, Server-Sent Events, chat, live updates
• Streaming: large files, video, streaming data
• High I/O concurrency: many parallel requests to external APIs without heavy business logic
• Serverless: Lambda/Cloud Functions — Node.js starts faster than PHP

Fastify over Express: 2–3 times faster on benchmarks, built-in JSON Schema validation, better TypeScript support, plugin architecture.

Typical realtime architecture: Laravel — core business logic and REST API. Node.js + Socket.io or ws — WebSocket server. Laravel publishes events to Redis Pub/Sub, Node.js subscribes and broadcasts to clients. This separation allows scaling the WebSocket server independently of the main app.

Go: microservices and high load

Go we use for:

• High-load microservices (>10,000 RPS)
• Background workers with strict latency requirements
• DevOps tools and CLI
• gRPC services in microservice architecture

Goroutines — thousands of times cheaper than OS threads. 10,000 concurrent connections on Go is normal on one server.

But Go is not a silver bullet. Development is slower than Laravel: more boilerplate, no ORM at Eloquent level, error handling with if err != nil everywhere. Justified only when performance is a real requirement, not an assumption.

Django and Python backend

Django with DRF (Django REST Framework) — for tasks where Python is needed: ML pipelines, data processing, integrations with AI tools.

Celery for background tasks — similar to Laravel Queue but more complex to configure. Celery Beat for cron tasks.

Django ORM vs raw SQL: ORM is convenient for CRUD. For analytical queries with multiple JOINs, window functions, and CTEs — connection.execute() with raw SQL is more readable and predictable.

Redis: not just cache

Redis in our projects plays multiple roles:

Redis Cluster for horizontal scaling. Sentinel for automatic failover on standalone setups.

Deployment and infrastructure

Docker + docker-compose — standard for local development and production. Each service in a container: PHP-FPM/Octane, Nginx, PostgreSQL, Redis, Queue Worker, Scheduler.

CI/CD via GitHub Actions:

1. Run tests (PHPUnit / Pest, Vitest, Playwright)
2. Build Docker image
3. Push to Container Registry
4. Deploy: docker pull → docker-compose up -d on server, or Kubernetes rolling update

Zero-downtime deploy for Laravel: php artisan down --secret=TOKEN is not needed with proper configuration. Strategy: new container starts next to the old one, Nginx switches traffic after health check, old container stops.

Monitoring: Sentry for exception tracking with alerting in Slack/Telegram. Grafana + Prometheus (or Grafana Cloud) for metrics: CPU, memory, request rate, queue depth, database connection count. Alerts on: error rate > 1%, p99 latency > 2s, queue depth > 1000 jobs.

What's included in turnkey work

• Architecture design (API documentation, DB schema, service diagram)
• Implementation according to agreed specification with code review
• CI/CD, monitoring, alerting setup
• Load testing (k6, wrk) with report
• Handover of source code, access, deployment instructions
• Training of customer's team (2-3 sessions)
• Warranty support for 1 month after delivery

Timeline benchmarks

Pricing is calculated individually after analyzing load, integrations, and business logic. Contact us for a free audit of your current backend — get an optimization plan in 2 days. Request a consultation.