cloudflare-d1

Deploy SQLite to Cloudflare's edge using D1, a serverless database service. Create a D1 database, bind it in wrangler.jsonc, apply migrations, and query from Workers. This approach runs your database across geo-distributed edge locations without managing infrastructure.

Create migration files, configure them in wrangler.jsonc, then run migrations before deployment. D1 applies migrations sequentially to your edge database, ensuring schema changes propagate consistently across replicas while supporting rollback capabilities.

Use prepared statements with bind() to safely parameterize queries on D1. Binding separates SQL logic from user input at the protocol level, preventing injection attacks while maintaining query performance at the edge.

D1 supports read replication and the Sessions API for geo-distributed consistency. Configure read replicas to distribute queries across regions, use Sessions API to maintain consistency for individual users, and apply PRAGMA optimize for performance tuning.

SQLite on D1 excels for edge workloads but has write constraints in distributed settings. Single-write-region design prevents concurrent writes across replicas; batch operations and prepared statements optimize throughput, but high-concurrency write scenarios require architecture adjustments.

Yes, D1 bindings require wrangler.jsonc configuration mapping your database to worker code. Once bound, access D1 through the env object passed to your worker handler, enabling direct SQL queries without separate connection management.