Home / Companies / Elastic / Blog / Post Details
Content Deep Dive

Schema on write vs. schema on read with the Elastic Stack

Blog post from Elastic

Post Details
Company
Date Published
Author
Tanya Bragin
Word Count
2,562
Company Posts That Month
36
Language
-
Hacker News Points
-
Post removed?
No
Summary

Elastic Stack (commonly known as ELK Stack) is a popular platform for storing and analyzing logs, offering two main approaches: "schema on read" and "schema on write." Schema on read allows users to apply structure to logs at search time, enabling ad hoc exploration but requiring repeated field extraction for ongoing reporting and dashboarding. Conversely, schema on write structures logs at the time of ingestion, which speeds up queries and aggregations by storing logs in a structured format, providing significant advantages for historical queries, real-time anomaly detection, and metrics correlation. This method also allows for better data quality verification, granular access control, and potentially lower storage needs by filtering unnecessary data upfront. The choice between these approaches depends on specific use cases and resource considerations, with Elastic Stack offering support for both methods to optimize workflows for different logging needs.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
Real-time 3 287 104 41 -22%
Observability 2 201 46 16 -33%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.