Cloudflare Workers and Hyperdrive with TanStack Start – Master.dev Blog

The post-quantum EO is an important milestone. Now it’s time to get to work

Sắc lệnh hành pháp 14409 của Mỹ yêu cầu các cơ quan liên bang và nhà thầu phải chuyển sang mã hóa hậu lượng tử (PQC) vào năm 2030 và xác thực hậu lượng tử vào năm 2031, nhằm ngăn chặn các cuộc tấn công "thu thập giờ đây giải mã sau". Cloudflare khuyến nghị cần làm rõ tiêu chuẩn "chuyển đổi", ưu tiên khả năng thích ứng mật mã (crypto agility) và thúc đẩy sự thống nhất toàn cầu về thuật toán NIST để tránh phân mảnh.

Lập trình viên nên đọc bài này để hiểu cách chuyển đổi sang các giải pháp mã hóa chống lượng tử (post-quantum) không chỉ là một yêu cầu pháp lý mà là một chiến lược bảo mật cấp hệ thống, giúp bảo vệ ứng dụng của bạn trước các mối đe dọa tương lai từ máy tính lượng tử trong thời gian ngắn nhất.

Cloudflare Workers: secrets and environments

A practical guide to managing configuration, secrets, and multiple deployment environments (staging, production) in Cloudflare Workers. Covers plain vars in wrangler.jsonc, encrypted secrets via Wrangler CLI, local development with .dev.vars, and per-environment secret scoping. Highlights a key gotcha: named environment blocks do not inherit top-level config, so bindings and triggers must be explicitly repeated in each environment block.

Cloudflare’s new policy pushes AI companies to pay for publishers’ content

Cloudflare is giving AI companies until September 15, 2026 to separate web crawlers used for traditional search from those used for AI training and agents. After that date, Cloudflare's default settings will block mixed-use crawlers from pages that host ads, affecting new customers, new sites, and all existing free customers. The policy aims to protect publishers' intellectual property and create a sustainable ecosystem where AI companies pay for content they use. Cloudflare is also evolving its Pay Per Crawl marketplace into a Pay Per Use model, allowing publishers to charge AI companies when their content creates value rather than just when it's fetched. Initial partners include Ceramic.ai and You.com. The announcement also calls out Google specifically for bundling search and AI crawling in ways that make it difficult for publishers to opt out without losing search visibility.

How to Build a Zero-Cost Personal Project with PHP, Wasmer, and Cloudflare

A step-by-step guide to hosting a PHP web project at zero cost using Wasmer (a WebAssembly-based cloud platform with sub-90ms cold starts), a free eu.org domain, and Cloudflare for DNS management. Covers creating a Wasmer account, deploying a PHP app from GitHub, setting up Cloudflare DNS with a CNAME record, and registering a free eu.org subdomain. The motivation is building a sustainable open-source project website that can outlive its creator without recurring costs.

Cloudflare wants to build the economic layer of the AI web

Cloudflare is positioning itself as the economic infrastructure layer between publishers and AI companies. The company announced Pay Per Use (publishers get paid when content appears in AI answers, not just when crawled), new crawler classification rules requiring AI companies to separate indexing, training, and agent traffic, and an Answer Engine Optimization dashboard. Starting September 15, new and free-tier sites will block AI training and agent crawlers by default on ad-supported pages. Cloudflare argues its existing position between websites and the internet gives it a unique advantage to manage access, attribution, and payments in the emerging AI-driven web economy.

How we built saga rollbacks for Cloudflare Workflows

Cloudflare Workflows now supports saga-style rollbacks, letting developers attach compensation logic directly to each step.do() call. When a multi-step workflow fails, registered rollback handlers execute in reverse step-start order, each running through Workflows' durable step machinery with retries, timeouts, and lifecycle events. The post explains the API design decisions (fluent vs. builder vs. options object), how rollback handlers are stored as callable stubs, how replay rebuilds handlers after engine restarts, and the key behavioral rules around ordering and eligibility for failed steps.

Cloudflare Workers observability: logs and traces

A practical guide to monitoring Cloudflare Workers in production using console.log, the observability configuration in wrangler.jsonc, and live log streaming with wrangler tail. Covers enabling persistent searchable logs, live tailing for active debugging, sampling strategies for high-traffic workers, and the difference between logs (what happened) and traces (why it was slow).