intermediate

OpenSearch

Use OpenSearch as an Elasticsearch-compatible search stack while evaluating ecosystem, hosting, and version compatibility.

OpenSearch is an open-source search and analytics fork of Elasticsearch 7.10, maintained by AWS and the community. APIs, query DSL, index concepts (shards, mappings, analyzers), and operational patterns are largely Elasticsearch-compatible — but plugins, security modules, and version lines diverge over time.

| Decision axis | What to compare | |---------------|-----------------| | Licensing | OpenSearch is Apache 2.0; Elasticsearch has proprietary SSPL/Elastic License tiers | | Hosting | AWS OpenSearch Service, self-managed, or other clouds | | Client compatibility | Check elasticsearch-js / opensearch-js and server version pairs | | Features | Security, alerting, ML plugins differ by distribution |

On interviews: explain when OpenSearch is a pragmatic choice (AWS stack, license posture, existing ES expertise) and what you verify before migration: query compatibility, index templates, snapshot tooling, and supported client libraries.

Common pitfalls: assuming 100% drop-in parity forever; mixing Elasticsearch 8+ features with OpenSearch; ignoring managed-service version lag; security plugin differences in multi-tenant setups; skipping a reindex test on production-like data.

The trade-off is ecosystem independence and license clarity versus smaller third-party plugin market and the need to track fork-specific release notes.

Checklist:

  • State ES compatibility baseline and divergence points.
  • Name hosting model (managed vs self-hosted).
  • Verify client library and API version matrix.
  • Plan migration with reindex and snapshot drills.
  • Compare security and observability tooling.