2
Pageserver to SQLite VFS adapter, or how applicable is neon's architecture to other engines
Source: neondatabase/neon#1958 · opened by @infogulch
Hi! I like neon's architecture design of splitting up storage work into pageserver and wal server components.
From afar it appears that the conceptual design of these components are somewhat general, which makes me curious if they could be used as a storage backend for other engines like MySQL or SQLite (or even as a backing store for ZFS?). I recall reading that the pageserver actually reconstructs valid postgresql pages on demand and the actual backing storage has a different format, so this may be more complex than pointing SQLite with a VFS adapter at the existing pageserver and calling it done.
From both an engineering-possibility perspective as well as project-priority perspective, what do you think about using neon's backing storage architecture for other database engines?
From afar it appears that the conceptual design of these components are somewhat general, which makes me curious if they could be used as a storage backend for other engines like MySQL or SQLite (or even as a backing store for ZFS?). I recall reading that the pageserver actually reconstructs valid postgresql pages on demand and the actual backing storage has a different format, so this may be more complex than pointing SQLite with a VFS adapter at the existing pageserver and calling it done.
From both an engineering-possibility perspective as well as project-priority perspective, what do you think about using neon's backing storage architecture for other database engines?
No pledges yet. Be the first to back this.
No comments yet.