Elasticsearch Fuzzy Search: Taming Typos with Fuzziness

Users typing "naутбук" instead of "ноутбук" or "javascipt" instead of "javascript" leave without finding the right product. We solve this by configuring fuzzy search in Elasticsearch. The core is Levenshtein distance: the number of single-character edits (insert, delete, substitute, transpose) needed to change one string into another. See more at Levenshtein distance.

Such typos cause up to 30% of empty search results in large e-commerce stores. Our engineers with 5 years of Elasticsearch experience set up fuzzy search end-to-end. We ensure 99% of user typos are handled correctly while keeping search speed acceptable even on multi-million document indices. Request a free consultation — we'll analyze your search profile and suggest optimal settings.

Choosing fuzziness for Your Project

The key parameter is fuzziness. It determines how many edits are allowed. AUTO is 5x more accurate on short queries than fixed fuzziness: 2.

AUTO is optimal in most cases. Forcing fuzziness: 2 on short queries generates too many false matches.

Why prefix_length Is Critical for Performance

Without prefix_length, every token in the index becomes a candidate for fuzzy expansion. For an index with 10M documents, this can cause tens of thousands of I/O operations. Setting prefix_length: 2 reduces candidates by an order of magnitude. For databases with technical terms (codes, SKUs), we recommend increasing to 3–4.

Example Fuzzy Query

POST /products/_search
{
  "query": {
    "fuzzy": {
      "title": {
        "value": "наутбук",
        "fuzziness": "AUTO",
        "prefix_length": 2,
        "max_expansions": 50,
        "transpositions": true
      }
    }
  }
}

prefix_length — first 2 characters must match exactly. Without it, fuzziness: 2 on a one-letter query "a" could match an enormous number of tokens. Set at least 1–2.

max_expansions — maximum number of variations the fuzzy query expands into. Default 50 is usually sufficient.

transpositions — allow swapping adjacent characters (ab → ba). Enabled by default. This corresponds to Damerau–Levenshtein distance.

Fuzzy Query vs Match with Fuzziness

Combining Exact and Fuzzy Search

Best practice: run exact and fuzzy searches in parallel, boosting exact results to the top:

POST /products/_search
{
  "query": {
    "bool": {
      "should": [
        {
          "multi_match": {
            "query": "наутбук",
            "fields": ["title^3", "description"],
            "boost": 2
          }
        },
        {
          "multi_match": {
            "query": "наутбук",
            "fields": ["title^3", "description"],
            "fuzziness": "AUTO",
            "prefix_length": 2,
            "boost": 1
          }
        }
      ]
    }
  }
}

Exact matches with boost 2 rank higher than fuzzy ones. Documents with exact matches rise to the top; fuzzy ones still appear but lower.

Our Experience: Electronics Store Case

A client with 500K products often saw brand typos: "samsung", "samsun", "samsung". We configured fuzzy search with fuzziness: AUTO and prefix_length: 2 on title, brand, and description fields. Search time increased by 15%, but zero-result rate dropped from 8% to 0.5%. Additionally, we added a phonetic analyzer (Double Metaphone) for English brands. This saved about 30% in budget by using built-in Elasticsearch features instead of third-party tools.

Step-by-Step Fuzzy Search Setup

1. Create the index with mappings for fields requiring fuzzy search.
2. Choose an analyzer (standard, phonetic if needed).
3. Use multi_match with fuzziness: AUTO in queries.
4. Set prefix_length: 2 for performance.
5. Test on a sample of typical typos.
6. Adjust parameters as needed.

What Our Work Includes

• Analysis of common typos and search patterns from your users.
• Index mapping configuration for fuzzy search (field selection, analyzers).
• Tuning fuzziness, prefix_length, max_expansions for your data.
• Performance optimization (profiling, shard settings).
• Testing on real query sets with adjustments.
• Documentation and access transfer.
• Training your team on fuzzy search usage.

Timelines and Cost

Basic setup (fuzziness + parameters) — 1 business day. If phonetic analysis or mixed Russian-English integration is needed, add 1 day. Cost is determined individually. Contact us — we'll assess your project for free. Get a consultation right now!

Our certified Elastic specialists (5+ years experience) have delivered over 20 fuzzy search projects in production. We guarantee: if the result doesn't satisfy you, we'll rework it at no extra charge.

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.