🔬 What's Novel
- First database protocol designed natively for HTTP/3 and QUIC multiplexed streams
- Integration of prepared query handles with QUIC 0-RTT for single-flight query execution
- Query-level connection migration for mobile and edge scenarios without losing cursor state
- Framework for CDN-integrated database query caching using ETag validation at the edge
🔧 Technical Approach
Phase 1 — Protocol Design
SkeinQL-over-QUIC: each query dispatched on a separate QUIC stream. Frame types for query submission, streaming results, prepared query handles, and ETag validation requests.
Phase 2 — 0-RTT Integration
First-flight data includes prepared query invocation. Replay protection for write safety — distinguish idempotent reads (safe for 0-RTT) from state-changing writes (require handshake).
Phase 3 — Connection Migration
Stateful query handling surviving QUIC connection migration. Query state (cursor position, transaction context) bound to connection ID and transferred seamlessly during migration events.
Phase 4 — CDN Integration
Edge caching where CDN nodes validate ETags and serve cached results without contacting the origin. CDN-aware query routing and cache warming strategies.
🧪 Hypotheses
QUIC multiplexing eliminates head-of-line blocking, measurably improving p99 latency for concurrent database queries.
0-RTT with prepared query handles reduces connection establishment overhead for serverless and edge deployment patterns.
QUIC connection migration enables seamless query continuation across network changes on mobile devices.
🔗 SkeinDB Integration
📚 Key References
- Iyengar & Thomson — "QUIC: A UDP-Based Multiplexed and Secure Transport" (RFC 9000, 2021)
- Bishop — "HTTP/3" (RFC 9114, 2022)