Skip to content

Commit 6f678d1

Browse files
committed
docs: micro edit for conceptual clarity
1 parent f3f17a4 commit 6f678d1

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

site/engineering/realtime-engine.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,9 +9,9 @@
99

1010
---
1111

12-
The Realtime Engine is the core of LinkedQL’s [live queries](/capabilities/live-queries). It is **an in-memory "compute + cache" layer** that lies between the storage layer and the application layer, transforming storage-level mutations — from WAL, binlog, or in-memory emitters — into logical events that materialize as live state, extending SQL’s reach from static queries to fully “live” queries.
12+
The Realtime Engine is the core of LinkedQL’s [live queries](/capabilities/live-queries). It is **an _in-memory_ compute + cache layer** that lies between the storage layer and the application layer, transforming storage-level mutations — from WAL, binlog, or in-memory emitters — into logical events that materialize as live state, extending SQL’s reach from static queries to fully “live” queries.
1313

14-
Unlike replica-based architectures that operate only against local databases or materialized stores, the engine is designed to operate seamlessly across storage backends — from local databases to traditional databases such as PostgreSQL and MySQL — allowing both to participate equally in the "realtime" space. LinkedQL thus brings reactivity into the realms of traditional SQL databases, erasing the local/remote distinction and making live queries a universal concept across storage backends.
14+
Unlike replica-based "live query" solutions that operate only against local databases or materialized stores, the engine is designed to operate seamlessly across storage backends — from local databases to traditional databases such as PostgreSQL and MySQL — allowing both to participate equally in the "realtime" space. LinkedQL thus brings reactivity into the realms of traditional SQL databases, erasing the local/remote distinction and making live queries a universal concept across storage backends.
1515

1616
This paper describes the engineering behind this design — from change detection and normalization to live, observable objects that self-update in real time.
1717

0 commit comments

Comments
 (0)