--- title: "Elasticsearch Was Never a Database" url: https://daily.dev/posts/elasticsearch-was-never-a-database-o9logokil source_url: https://www.paradedb.com/blog/elasticsearch-was-never-a-database type: article source: "Hacker News" published: 2026-01-16T23:21:59.737Z updated: 2026-01-16T23:22:24.331Z tags: ["database", "postgresql", "elk"] reading_time: 8 upvotes: 2 comments: 0 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Elasticsearch Was Never a Database **[Hacker News](https://daily.dev/sources/hn)** · 8 min read · 2 upvotes · 0 comments ## Summary Elasticsearch excels as a search engine but fails as a primary database due to fundamental architectural limitations. It lacks atomic transactions beyond single documents, requires full reindexing for schema changes, has limited join support, and doesn't provide the durability guarantees expected from a system of record. Teams often start using Elasticsearch as a secondary index but gradually shift it to become their primary datastore, encountering consistency issues, operational complexity, and workarounds that negate the initial simplification. The article argues Elasticsearch should remain what it was designed to be—a search layer—while databases like Postgres handle transactional workloads. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Similar posts on daily.dev - [Just Use Postgres](https://daily.dev/posts/just-use-postgres-ueffslq3a) · Lobsters · 0 upvotes · 0 comments --- Tags: [#database](https://daily.dev/tags/database), [#postgresql](https://daily.dev/tags/postgresql), [#elk](https://daily.dev/tags/elk) [View this post on daily.dev](https://daily.dev/posts/elasticsearch-was-never-a-database-o9logokil)