Card #369 · Elastic (Elasticsearch / Kibana)
Using Elasticsearch as a primary relational database
Merchants are struggling with using Elasticsearch as a primary data store for relational business domains. This leads to critical issues with referential integrity, data inconsistency due to aggressive denormalization, and high maintenance overhead for custom DAO layers.
Pain score
0.50/ 1.00 · weighted product of four components
Reach0.32distinct authors (log-normalized)
Recency0.97freshness decay, half-life months
Engagement1.00upvotes + comments, normalized
Monetization0.50willingness-to-pay cues in evidence
§ Evidence — 4 verified quotes
ES has no foreign keys, no unique constraints, no cross-document transactions. The application stores inter-entity relationships as string IDs embedded in documents, with zero enforcement at the database level.
Since ES can't join across document types at query time, the original developers denormalized aggressively.
Every new feature, every bug fix, every onboarding of a new developer pays a tax for this layer's existence.
users could be seeing incomplete data without any error being raised — and we'd never know.
Comments are a Pro feature — join the conversation, share what you've shipped, hear what others are building.
Upgrade to Pro