Why Lesan
TL;DR — Lesan treats relationships as self-maintaining data: they're defined one-directional but embedded bi-directionally in storage, and Lesan keeps every embedded copy in sync automatically. Reads that cost other stacks ~2.5 million documents cost Lesan ~25 thousand. This page is the full argument, extracted from the companion article at examples/whyLesan/article.md.
The Nature of Data
TL;DR — Real-world data follows a universal law: expensive updates and deletions are rare, and cheap ones are frequent. Lesan's embedded, self-syncing relationships turn that asymmetry into the win you saw in Why Lesan. This page walks the two archetypal real-world cases — the best case (a blog) and the worst case (population statistics) — and shows how the nature of your data models decides everything.