Redis

Serverless Zero-Database Web App with Client-Side Images

A developer describes how they built Rankly, a Tier List Maker, as a stateless, zero-database web app that scales to large user counts by performing image processing and export entirely in the browser. The architecture uses the HTML5 File API and URL.createObjectURL to avoid uploads, keeps application state in local memory (React), and synthesizes high-resolution PNG exports with the HTML5 Canvas API. By serving only static HTML/CSS/JS from free CDN platforms (e.g., Cloudflare, Vercel), the approach aims to eliminate hosting costs, reduce maintenance and legal compliance burdens, and improve privacy and responsiveness compared with traditional server-based pipelines that rely on S3, databases, or headless browsers for exports.

ContextOS: AST-aware Retrieval for AI in Large Codebases

The article argues that failures of AI coding assistants in large repositories are retrieval problems, not model reasoning issues. The author introduces ContextOS, a local-first context engine that preserves code structure by using Tree-sitter to extract AST-aware chunks (functions, classes, interfaces), prioritizes BM25 lexical search via SQLite FTS5 with a MiniLM ONNX fallback for semantic matching, and applies query-aware context compression. In benchmarks, ContextOS reached 98% file-level recall on 100 exact-function queries against the Redis 7.x C codebase with an average 589 tokens per query, and ~100% accuracy on React/Next.js with ~280 tokens per query. ContextOS exposes a Model Context Protocol (MCP) server and is available on GitHub.

Architecting Reliable SaaS Billing with Stripe

This technical how-to explains building a production-grade SaaS billing system with Stripe. It argues against synchronous webhook handling and recommends an asynchronous architecture using a message queue and worker processes to handle out-of-order and retried webhooks. The article details idempotent webhook reception using Redis keys (with a 24-hour TTL), idempotent usage reporting via Stripe Billing Meter events with deterministic identifiers, and safe subscription upgrades using proration settings (including billing_cycle_anchor: 'unchanged'). It also covers handling failed payments by respecting Stripe's past_due status and Smart Retries, performance best practices (indexing, avoiding N+1 queries), and operational safeguards like dead-letter queues.