Your Read Model Doesn't Always Need a Database
The article discusses the concept of read models in event-sourced systems and challenges the assumption that a database is necessary for them. It argues that read models can be kept in memory, making them disposable and easily rebuildable from event data. This approach allows for flexibility in engineering choices regarding data storage and access patterns.
- ▪Read models in event-sourced systems do not need to be stored in a database.
- ▪They can be kept in memory and rebuilt from event data when necessary.
- ▪This method allows for multiple read models tailored to different queries without the constraints of traditional databases.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Eventsourcingdb |
| Canonical URL | https://docs.eventsourcingdb.io/blog/2026/05/21/your-read-model-doesnt-always-need-a-database/ |
| Publication time | Thu, 21 May 2026 04:36:42 +0000 |
| Retrieval time | 2026-05-21T05:05:03.495Z |
| Last seen | 2026-05-21T05:05:03.495Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 2PZIuCmjh3QO |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Your Read Model Doesn't Always Need a Database¶ Sooner or later, every team building an event-sourced system runs into the same question: which database should we use for the read model? The textbook answer is reassuringly pragmatic. It depends. Pick the tool that fits the access pattern. Relational if you need joins and ad-hoc queries, document-oriented if your data is hierarchical, key-value if you mostly look things up by ID, a graph database for relationships, a spatial database for geodata, and so on. That advice is sound, and yet it quietly assumes something that nobody ever questions: that there has to be a database in the first place. There's one option that almost never makes it onto that list, and it's the one that turns the whole question on its head.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Eventsourcingdb.
Discussion
0 commentsMore from Eventsourcingdb
