Running SQLite in the browser with sql.js and WASM — a practical guide with Google Drive sync

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant Common SOC 2 Failures (Real World) Stop Vibe-Checking Your AI App: A Practical Guide to Evals How to Use SonarQube and SonarScanner Locally to Level Up Your Code Quality Your Next To-Do App Is Dead — I Replaced Mine with an OpenClaw AI Sign a Nostr event in 60 lines of Python using coincurve — no nostr-sdk, no nbxplorer, no rust toolchain ITGC Audit Explained Like You’re in Big 4 Patch Tuesday abril 2026: Microsoft parcha 163 vulnerabilidades y un zero-day en SharePoint Stop scraping everything: a better way to track competitor price changes Listing on MCPize + the Official MCP Registry while routing payments OUTSIDE the marketplace — how I kept 100% of my x402 revenue Building an AI-Powered Risk Intelligence System Using Serverless Architecture Why We Ripped Function Overloading Out of Our AI Toolchain Testing AI-Generated Code: How to Actually Know If It Works SaaS Churn Is Killing Your Business. Here Is What to Do About It (Without a Support Team) The Speed of AI Is No Longer Linear - And Self-Improving Models Are Why How to Implement RBAC for MCP Tools: A Practical Guide for Engineering Teams From Standard Quote to Persuasive Proposal: AI Automation for Arborists I built a CLI that scaffolds complete multi-tenant SaaS apps Axios CVE-2025–62718: The Silent SSRF Bug That Could Be Hiding in Your Node.js App Right Now The dashboard that ended our friendship Data Pipelines Explained Simply (and How to Build Them with Python) The Hidden Cost of AI Systems Nobody Talks About. undefined vs undeclared, and how typeof behaves Switching from file-based jobs to NATS/Kafka in Rust without changing code io_uring Adventures: Rust Servers That Love Syscalls Why Agentic AI is Killing the Traditional Database The POUR principles of web accessibility for developers and designers Quantum Neural Network 3D — A Deep Dive into Interactive WebGL Visualization How To Install Caveman In Codex On macOS And Windows Automation Pipeline Reliability: Why Your Workflow Breaks When Nobody Is Watching I Built an 'Open World' AI Coding Agent — It Works From ANY Folder From Freelancing to Product: A Tech Service Company's SaaS Transformation China's AI Giants: Adding Tencent Hunyuan & ByteDance Doubao to AI University (74 Providers) On the Vibe Coders and Their Lies clerk: Auto-Summarize Your Claude Code Sessions AI Weekly — 2026/04/10–04/17 | The Model Lockdown Is Here, but the Toolchain Is the Real Battleground AI 週報 — 2026/04/10–2026/04/17 模型封鎖潮來了，但工具鏈才是真戰場 Maybe this is how Open-Source apps are born... 🚀 Fine-Tune LLMs with LoRA and QLoRA: 2026 Guide tRPC v11 + Next.js App Router: End-to-End Type Safety Without the Boilerplate ShadCN UI in 2026: Why I Stopped Installing Component Libraries and Started Owning My Components SaaS Billing in React Server Components: Stripe + Supabase Without a Single `useEffect` Join our DEV Weekend Challenge — $1,000 in Prizes Across TEN winners! Submissions Due April 20 at 6:59 AM UTC. Implementing FSRS Spaced Repetition in Flutter + Supabase — Adding Memory Science to an AI Learning App "I Texted My Localhost From the Train — Claude Code Fixed the Bug Before I Got Home" I Built a Sales Prep AI and It Went Deeper Than Expected Design to Code #2: One JSON, Eleven Outputs Solving the 100M-Row Problem: A Summary Table Pattern for High-Volume Push Notification Logs Flutter Web With Wasm: What Actually Changes For Developers I Built 50 Royalty-Free Soundtracks for My Side Project in a Weekend Using AI Music Generation The Vibe Coding Security Checklist: 7 Things to Check Before You Ship Stop Letting Googlebot Guess Fix Your React App's SEO Right Desconstruindo o Streaming do LinkedIn: Como Criar um Engine de Extração de Vídeo de Alta Performance com HLS e FFmpeg (EDA Part-1) EDA (Exploratory Data Analysis) Explained With Real Life — Why Looking at Your Data Is the Most Important Step in Machine Learning Brand Relationship Management at Scale: Our 4-Touch Outreach System for 200+ Brands Why String.fromEnvironment() Might Return an Empty String in Dart JGuardrails 1.0.0 — Hardening Java LLM Apps Against Jailbreaks, Toxicity, and Prompt Injection Plan and Schedule a Full Week of Threads Content From One Claude Conversation Coding Cat Oran Ep3, Five Tables Changed Everything Updated: BFF Pattern I'm done watching freelancers get buried by 200 proposals. So I'm building the alternative. This is my first post BFS Algorithm in Java Step by Step Tutorial with Examples Tracking LLM Pricing Monthly: An Open Dataset for 22 AI Models How We Measure Content ROI on a Comparison Site: Revenue Attribution Without Perfect Data Introducing Nova AI Ops: The AI-Native Operating System for SRE Teams I built a free desktop video downloader for Windows — Grabbit How Talkie OCR Helps Vision-Impaired & Dyslexic Users Read the World Around Them VRCFaceTracking安装和iPhone面捕配置教程，有bug Even CrowdStrike Can't See Your Agents The Automation Gold Rush: What n8n Workflows and Claude Are Opening Up for Developers Right Now

Deeshan Shar · 2026-04-28 · via DEV Community

Most tutorials on client-side data storage reach for IndexedDB, localStorage, or a third-party sync service. This one goes somewhere different: a real SQLite database, running as WebAssembly in the browser, with the database file living on the user's own Google Drive. This is the setup behind <a href="https://overtimeiq.vercel.app?ref=devto" rel="noopener noreferrer">OvertimeIQ</a> — but everything in this article stands alone as a practical reference. You don't need to care about overtime tracking for any of this to be useful. By the end, you'll know how to: <ul> <li>Initialize sql.js and run real SQL in the browser</li> <li>Persist the database across page reloads via localStorage</li> <li>Upload and download the database file from Google Drive</li> <li>Handle sync conflicts correctly</li> <li>Protect against data corruption on interrupted uploads</li> </ul> <h2> Why SQLite in the browser? </h2> Before we write any code, it's worth asking why you'd reach for SQLite instead of IndexedDB or a cloud-synced store. The answer is portability. A SQLite database is a single binary file. You can open it on any device, in any SQLite-compatible tool, without installing anything. You can attach it to an email, drop it in Dropbox, or — as we'll do here — store it on Google Drive. The user owns a file, not a schema locked inside a browser's internal storage. For apps where user data portability matters — personal finance tools, health tracking, anything sensitive — this is a meaningful architectural choice, not just a curiosity. The trade-off: sql.js ships a ~1.5MB WASM binary. We'll deal with that below. <h2> Setting up sql.js </h2> Install the package: <div class="highlight js-code-highlight"> <pre class="highlight shell"><code>npm install sql.js </code></pre> </div> The WASM binary needs to be accessible at a URL your code can load. Copy it into your <code>public</code> folder at build time: <div class="highlight js-code-highlight"> <pre class="highlight javascript"><code>// vite.config.js import { defineConfig } from 'vite' import { viteStaticCopy } from 'vite-plugin-static-copy' export default defineConfig({ plugins: [ viteStaticCopy({ targets: [ { src: 'node_modules/sql.js/dist/sql-wasm.wasm', dest: '' } ] }) ] }) </code></pre> </div> Now initialise sql.js. This is async — the WASM binary has to load before you can do anything: <div class="highlight js-code-highlight"> <pre class="highlight javascript"><code>// lib/db.js import initSqlJs from 'sql.js' let db = null export async function initDB(existingBuffer = null) { const SQL = await initSqlJs({ locateFile: file => `/${file}` // points to /sql-wasm.wasm in public/ }) if (existingBuffer) { // Restore from a saved buffer (localStorage or Drive download) db = new SQL.Database(new Uint8Array(existingBuffer)) } else { // Fresh database db = new SQL.Database() } return db } </code></pre> </div> Lazy loading matters here. Don't initialise the database on app load. Initialise it on first access. With a Service Worker caching the WASM binary after the first load, subsequent loads are instant — but you still don't want to block your UI render on a 1.5MB download for users on their first visit. <h2> Running SQL </h2> sql.js has two main operations: <div class="highlight js-code-highlight"> <pre class="highlight javascript"><code>// For SELECT — returns an array of result objects export function runQuery(sql, params = []) { const stmt = db.prepare(sql) stmt.bind(params) const rows = [] while (stmt.step()) { rows.push(stmt.getAsObject()) } stmt.free() return rows } // For INSERT / UPDATE / DELETE — no return value export function execSQL(sql, params = []) { const stmt = db.prepare(sql) stmt.run(params) stmt.free() } // Convenience wrapper for single-row queries export function getOne(sql, params = []) { const rows = runQuery(sql, params) return rows.length > 0 ? rows[0] : null } </code></pre> </div> Usage is exactly what you'd expect from a SQL library: <div class="highlight js-code-highlight"> <pre class="highlight javascript"><code>execSQL( 'INSERT INTO logs (job_id, date, start_time, end_time, duration_hours, location) VALUES (?, ?, ?, ?, ?, ?)', [1, '2025-04-14', '20:00', '23:30', 3.5, 'office'] ) const logs = runQuery( 'SELECT * FROM logs WHERE date >= ? ORDER BY date DESC', ['2025-01-01'] ) </code></pre> </div> <h2> Schema migrations </h2> You need a migration runner. The pattern I use: a <code>schema_version</code> table with a single integer, and a list of migration functions keyed by version number. <div class="highlight js-code-highlight"> <pre class="highlight javascript"><code>const MIGRATIONS = { 1: (db) => { db.run(` CREATE TABLE IF NOT EXISTS jobs ( id INTEGER PRIMARY KEY AUTOINCREMENT, name TEXT NOT NULL, hourly_rate REAL NOT NULL, weekend_multiplier REAL DEFAULT 1.5, holiday_multiplier REAL DEFAULT 2.0, work_start TEXT NOT NULL, work_end TEXT NOT NULL, color TEXT DEFAULT '#3B8BD4', is_default INTEGER DEFAULT 0, created_at TEXT NOT NULL ) `) db.run(` CREATE TABLE IF NOT EXISTS logs ( id INTEGER PRIMARY KEY AUTOINCREMENT, job_id INTEGER REFERENCES jobs(id), date TEXT NOT NULL, start_time TEXT NOT NULL, end_time TEXT NOT NULL, crosses_midnight INTEGER DEFAULT 0, duration_hours REAL NOT NULL, location TEXT NOT NULL, notes TEXT, created_at TEXT NOT NULL, updated_at TEXT NOT NULL ) `) db.run('CREATE INDEX IF NOT EXISTS idx_logs_date ON logs(date)') } } export async function runMigrations(db) { db.run('CREATE TABLE IF NOT EXISTS schema_version (version INTEGER NOT NULL)') const row = getOne('SELECT version FROM schema_version') const currentVersion = row ? row.version : 0 const pendingVersions = Object.keys(MIGRATIONS) .map(Number) .filter(v => v > currentVersion) .sort((a, b) => a - b) for (const version of pendingVersions) { MIGRATIONS[version](db) if (currentVersion === 0) { execSQL('INSERT INTO schema_version (version) VALUES (?)', [version]) } else { execSQL('UPDATE schema_version SET version = ?', [version]) } } } </code></pre> </div> Run migrations immediately after initializing the database, before anything else touches it. <h2> Serializing to Uint8Array </h2> This is the key operation that makes everything else work. sql.js can export the entire database state as a <code>Uint8Array</code> — a binary blob that is identical to what SQLite would write to disk. <div class="highlight js-code-highlight"> <pre class="highlight javascript"><code>export function serializeDB() { return db.export() // Returns Uint8Array } </code></pre> </div> That <code>Uint8Array</code> is your database file. Everything that follows — localStorage persistence, Drive upload, Drive download — is just moving that blob around. <h2> localStorage persistence </h2> After every write operation, serialize and save: <div class="highlight js-code-highlight"> <pre class="highlight javascript"><code>const DB_STORAGE_KEY = 'otiq_db' export function saveDB() { const buffer = serializeDB() // Convert Uint8Array to a regular array for JSON serialisation localStorage.setItem(DB_STORAGE_KEY, JSON.stringify(Array.from(buffer))) // Trigger the Drive upload debounce (see below) scheduleDriveUpload() } export function loadFromLocalStorage() { const stored = localStorage.getItem(DB_STORAGE_KEY) if (!stored) return null return new Uint8Array(JSON.parse(stored)) } </code></pre> </div> On app load, check localStorage first. If there's a saved buffer, restore from it. Then compare with Drive to decide whether to download a newer version. Storage size note: A SQLite file with thousands of rows will likely stay well under 5MB — comfortably within localStorage limits. If your use case could grow very large, consider using the Origin Private File System instead, but for personal data tools localStorage is generally fine. Always call <code>navigator.storage.persist()</code> on first load to request durable storage — without it, browsers can evict localStorage under storage pressure. <div class="highlight js-code-highlight"> <pre class="highlight javascript"><code>async function requestDurableStorage() { if (navigator.storage && navigator.storage.persist) { const granted = await navigator.storage.persist() if (!granted) { // Show a warning banner — Drive sync is the backup showStorageWarning() } } } </code></pre> </div> <h2> Google Drive as cloud sync </h2> The Drive setup requires Google OAuth with the <code>drive.file</code> scope — the minimal scope that grants access only to files this specific app created. It cannot read other Drive files. This is the right choice for privacy-sensitive apps. I'll cover the full PKCE OAuth flow in the next article in this series. For now, assume you have a valid <code>access_token</code>. <h3> Finding the database file </h3> On login, search for an existing database file: <div class="highlight js-code-highlight"> <pre class="highlight javascript"><code>async function findDBFile(accessToken) { const response = await fetch( `https://www.googleapis.com/drive/v3/files?q=name='overtimeiq.db'&fields=files(id,modifiedTime)`, { headers: { Authorization: `Bearer ${accessToken}` } } ) const data = await response.json() return data.files?.[0] ?? null // { id, modifiedTime } or null } </code></pre> </div> <h3> Creating the file (first time) </h3> <div class="highlight js-code-highlight"> <pre class="highlight javascript"><code>async function createDBFile(accessToken, dbBuffer) { const metadata = { name: 'overtimeiq.db', mimeType: 'application/octet-stream' } const formData = new FormData() formData.append('metadata', new Blob([JSON.stringify(metadata)], { type: 'application/json' })) formData.append('file', new Blob([dbBuffer], { type: 'application/octet-stream' })) const response = await fetch( 'https://www.googleapis.com/upload/drive/v3/files?uploadType=multipart&fields=id', { method: 'POST', headers: { Authorization: `Bearer ${accessToken}` }, body: formData } ) const data = await response.json() return data.id // Store this file ID in settings.drive_file_id } </code></pre> </div> <h3> Downloading the file </h3> <div class="highlight js-code-highlight"> <pre class="highlight javascript"><code>async function downloadDBFile(accessToken, fileId) { const response = await fetch( `https://www.googleapis.com/drive/v3/files/${fileId}?alt=media`, { headers: { Authorization: `Bearer ${accessToken}` } } ) const buffer = await response.arrayBuffer() return new Uint8Array(buffer) } </code></pre> </div> <h2> The sync decision logic </h2> On every app load after login, you need to decide: use the local database, or download from Drive? <div class="highlight js-code-highlight"> <pre class="highlight javascript"><code>async function syncOnLogin(accessToken) { const driveFile = await findDBFile(accessToken) if (!driveFile) { // First time — upload local DB and store the file ID const buffer = loadFromLocalStorage() ?? serializeDB() const fileId = await createDBFile(accessToken, buffer) execSQL('UPDATE settings SET drive_file_id = ? WHERE id = 1', [fileId]) execSQL('UPDATE settings SET last_synced_at = ? WHERE id = 1', [new Date().toISOString()]) return } const driveModifiedTime = new Date(driveFile.modifiedTime).getTime() const localSyncedAt = getOne('SELECT last_synced_at FROM settings WHERE id = 1')?.last_synced_at const localTime = localSyncedAt ? new Date(localSyncedAt).getTime() : 0 const diff = Math.abs(driveModifiedTime - localTime) if (diff < 30_000) { // Within 30 seconds — same-device multi-tab edge case, no action return } if (driveModifiedTime > localTime) { // Drive is newer — download and replace const buffer = await downloadDBFile(accessToken, driveFile.id) await reinitializeFromBuffer(buffer) // Re-init sql.js with the new buffer showToast('Synced from Drive') } else { // Local is newer — upload await uploadDBToDrive(accessToken, driveFile.id) } execSQL('UPDATE settings SET last_synced_at = ? WHERE id = 1', [new Date().toISOString()]) } </code></pre> </div> Conflict resolution policy: When in doubt, prefer the Drive copy. Drive is the source of truth. If <code>modifiedTime</code> comparison is inconclusive (e.g., clock skew between devices), take the Drive copy and show a toast: "Synced from Drive — local changes from this session may have been overwritten." <h2> The upload safety pattern </h2> Never upload directly to <code>overtimeiq.db</code>. Upload to a temp file first, then rename atomically. A browser crash, network interruption, or error mid-upload should never corrupt the live database. <div class="highlight js-code-highlight"> <pre class="highlight javascript"><code>async function uploadDBToDrive(accessToken, fileId) { const buffer = serializeDB() // Step 1: Upload to temp file const tempMetadata = { name: 'overtimeiq_tmp.db' } const formData = new FormData() formData.append('metadata', new Blob([JSON.stringify(tempMetadata)], { type: 'application/json' })) formData.append('file', new Blob([buffer], { type: 'application/octet-stream' })) const uploadResponse = await fetch( `https://www.googleapis.com/upload/drive/v3/files/${fileId}?uploadType=multipart`, { method: 'PATCH', headers: { Authorization: `Bearer ${accessToken}` }, body: formData } ) if (!uploadResponse.ok) throw new Error('Upload failed') // Step 2: Rename temp file to live file atomically await fetch( `https://www.googleapis.com/drive/v3/files/${fileId}`, { method: 'PATCH', headers: { Authorization: `Bearer ${accessToken}`, 'Content-Type': 'application/json' }, body: JSON.stringify({ name: 'overtimeiq.db' }) } ) } </code></pre> </div> If Step 1 succeeds but Step 2 fails, the user has a temp file but the live file is intact. On the next sync, the timestamp comparison will catch the discrepancy and prompt a re-upload. <h2> Debouncing the Drive upload </h2> You don't want to upload to Drive on every keypress or every individual log entry mutation. Debounce it: <div class="highlight js-code-highlight"> <pre class="highlight javascript"><code>let driveUploadTimeout = null export function scheduleDriveUpload() { if (driveUploadTimeout) clearTimeout(driveUploadTimeout) driveUploadTimeout = setTimeout(async () => { const accessToken = getAccessToken() // From your auth store const fileId = getOne('SELECT drive_file_id FROM settings WHERE id = 1')?.drive_file_id if (accessToken && fileId) { await uploadDBToDrive(accessToken, fileId) execSQL('UPDATE settings SET last_synced_at = ? WHERE id = 1', [new Date().toISOString()]) } }, 10_000) // 10 seconds after the last write } </code></pre> </div> The localStorage write happens synchronously on every mutation — data is safe locally the instant you write it. The Drive upload is fire-and-forget with a 10-second debounce so a bulk import (100 rows at once) only triggers one upload. <h2> Putting it all together </h2> The initialization sequence on app load: <div class="highlight js-code-highlight"> <pre class="highlight javascript"><code>async function initializeApp() { // 1. Try to restore from localStorage const storedBuffer = loadFromLocalStorage() // 2. Initialize sql.js with the stored buffer (or fresh) await initDB(storedBuffer) // 3. Run schema migrations await runMigrations(db) // 4. Seed defaults if this is the first launch if (!getOne('SELECT id FROM jobs WHERE id = 1')) { seedDefaultJob() seedHolidays() } // 5. Request durable storage await requestDurableStorage() // 6. If authenticated, sync with Drive const accessToken = getStoredAccessToken() if (accessToken) { await syncOnLogin(accessToken) } } </code></pre> </div> <h2> What this doesn't cover </h2> This article focused on the storage and sync layer. Two things worth a separate deep dive: The Google OAuth PKCE flow — how to get the <code>access_token</code> and <code>refresh_token</code> without a client secret, and how to silently refresh the token mid-session. That's the next article in this series. The midnight rate calculation — how to correctly split a shift that crosses midnight across two different rate multipliers, including the December 31 → January 1 edge case. I'll cover that in a later article on the earnings engine. <h2> The case for this architecture </h2> The pattern here — SQLite on the user's cloud storage, managed entirely client-side — works well for a specific category of app: personal data tools where the data is sensitive, the user count is small, and data portability is a first-class feature. It's not the right choice for collaborative tools, apps with large binary assets, or anything requiring server-side processing of the data. But for personal productivity software, financial tracking, health logging, or any domain where "your data should be yours" is a meaningful promise — this architecture delivers it genuinely, not as marketing copy. The database is a file. The user can open it in DB Browser for SQLite today. They'll be able to open it in twenty years. That kind of portability is hard to promise with any other approach. I'm building <a href="https://overtimeiq.vercel.app?ref=devto" rel="noopener noreferrer">OvertimeIQ</a> — a personal overtime tracker where your data lives on your own Google Drive. This is part of an ongoing series documenting the technical decisions behind the build. The <a href="https://dev.to/deeshansharma/i-tried-to-build-a-personal-saas-with-zero-backend-heres-where-that-strategy-hits-a-wall-210i">first article in the series</a> covers the overall architecture and where the "no backend" approach hits a ceiling.

此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。原文来自 — 版权归原作者所有。

推荐订阅源

DEV Community