Skip to content
pubscout

elastic_client

0.3.15, released 3 years ago by agilord.com

Dart bindings for the ElasticSearch HTTP API.

WASM-ready
$ flutter pub add elastic_client
Source repository

What it does

Provides Dart bindings to interact with the ElasticSearch HTTP API for full-text search and document operations. Allows developers to run queries, count documents, and work with aggregations from Dart applications.

AI-written summary of version 0.3.15, based on the package's README and metadata. Report an inaccuracy

Use it when

  • You need to communicate with an ElasticSearch backend from a Dart or Flutter application.
  • You want to perform full-text searches, count items, or run aggregations against ElasticSearch.

Skip it when

  • You are looking for an integrated local database or key-value storage solution on the device.
  • You need a robust, cluster-aware transport layer with advanced automatic failover and node selection.

Strengths

  • Enables direct integration with ElasticSearch from Dart.
  • Supports various query types like match phrase, regexp, and knn.

Weaknesses

  • API is expected to change and subject to breaking changes.
  • Lacks cluster-aware transport features such as latency-aware or routing-aware node selection.

Setup

Kind
Pure Dart
Effort
Low
Code generation
No
Direct dependencies
3

Add the package as a dependency and configure connectivity to your ElasticSearch instance.

not documented

Alternatives

Packages that do the same job and could replace elastic_client.

  • typesense

    Dart client library for accessing the HTTP API of the Typesense search engine.

  • http2

    An HTTP/2 implementation in Dart for low-level transport and pooled HTTP/2 requests.

  • native_workmanager

    Background task scheduling for Flutter — 25+ native workers (HTTP, image, crypto, file), task chains, zero Flutter Engine overhead.

  • fetch_api

    Dart bindings for the JavaScript Fetch API, enabling web‑only HTTP requests with streaming and abort support.

Works with

Packages commonly used together with elastic_client: ones it builds on, ones built on it, and its own family.