Proposal: Migrate Core Storage to Cloudflare D1 + KV Cache

[miantiao-me]

Background

The current KV-only architecture has reached its limits regarding feature expansion.
Many requested features (like sorting by time or filtering by domain) are becoming impossible to implement elegantly because KV lacks native query capabilities.

To support the long-term development of Sink, I plan to migrate the core data storage to Cloudflare D1 (SQLite).

What problems will this solve?

By introducing SQL capabilities, we can resolve several long-standing issues at once:

• Sorting & Pagination
  Native support for ORDER BY created_at, finally allowing the dashboard to show the newest links first.

• Advanced Filtering
  Support for filtering by domain, expiration time, and similar attributes.

• Flexibility
  Remove key format restrictions (supporting slugs with /)
  and enable features like tagging.

Architecture: D1 + KV Cache

To ensure we don't sacrifice redirection speed, I plan to use a D1 + KV (Cache) hybrid approach:

• Management (Admin / API)
  Reads and writes go to D1 as the Source of Truth, providing full sorting and filtering capabilities.

• Redirection
  Prioritizes reading from KV Cache (synced when writing to D1) to maintain extreme performance and low latency.

Impact

1. Breaking Change
   The current KV cursor-based pagination API will be deprecated in favor of SQL-based pagination.

2. Data Migration
   A migration script will be provided to import existing KV data into D1.

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• Sort links in dashboard by creation date #102: Sort links in dashboard by creation date - Your D1 migration proposal would enable SQL ORDER BY functionality for sorting
• [Feature Request] Filter data by Domain #181: Filter data by Domain - D1 would enable advanced filtering queries by domain
• 'slash' not supported in Slug #157: 'slash' not supported in Slug - You explicitly mention this would be resolved after D1 migration
• [Feature request]: Add tags to organization the links #38: Add tags to organization the links - D1 would enable tag support with relational data

Additionally, your proposal may also address:

• Where do expired short links go? #142: Where do expired short links go? - D1 enables better expiration management
• Users/Multiple tokens #104: Users/Multiple tokens - D1 would support user management capabilities

Feel free to ignore if none of these address your specific case.