AI Weekly Malaysia

Tailscale traced a series of outages starting August 2025 to a 16-year-old bug in SQLite's write-ahead log checkpointing process. After a six-month investigation, SQLite maintainers had to build a new VFS activity logging tool (funded by Tailscale) just to reproduce the issue, which resisted all initial debugging attempts. Tailscale has used SQLite as its primary database since 2022, and the corruption first surfaced during their routine snapshot-to-S3 backup pipeline.

Why: If you ship SQLite in production with WAL mode and periodic snapshot backups, this postmortem is a direct warning that WAL checkpoint corruption can surface silently and be extremely hard to reproduce. Database learners and builders should read the Tailscale write-up before assuming SQLite's WAL is bulletproof in backup-heavy workloads, and consider whether their own backup pipeline could hit the same edge case now that the bug is documented.

A 16-year-old SQLite write-ahead log (WAL) checkpointing bug caused recurring database corruption in Tailscale's tailnet infrastructure starting August 2025, taking six months to diagnose. Tailscale funded SQLite maintainers to build a new virtual file system logging tool to reproduce the issue, which engineer Alex Chan described as resisting all initial debugging attempts including checks on POSIX locks, memory management, and thread safety.

Why: If you ship SQLite as a primary database under continuous backup snapshots, this postmortem is a concrete lesson in how deep storage-layer bugs can masquerade as application-level corruption for months. The debugging methodology—systematically ruling out POSIX lock, memory, and threading theories before isolating checkpointing—is worth studying before you hit a similar wall. The fact that SQLite maintainers themselves had to write new tooling to reproduce it should reset expectations about how 'reliable and well-known' doesn't mean 'bug-free' for critical infrastructure.

An opinion piece arguing that hyperscalers are using AI-driven demand to lock up the enterprise hardware supply chain, leaving businesses little choice but to rent compute back from them. Nutanix CEO Rajiv Ramaswami noted the fastest way to get a new server is now to rent from a hyperscaler; Micron, SK Hynix, and Seagate have long-term supply deals favoring their largest customers; AMD has sweetheart deals with OpenAI and Meta. AWS CEO Andy Jassy says AWS recoups server spend in under three years on assets with 5-6 year useful lives, with datacenters designed to last 30 years.

Why: If hyperscalers continue cornering hardware supply, bootstrapping or cost-sensitive Malaysian startups that planned to own on-prem or colo gear will face longer delivery times and higher prices, making cloud rental the de facto path. Founders should model infrastructure costs assuming hyperscaler pricing power persists rather than betting on cheaper self-hosted hardware, and consider locking in longer-term cloud commitments if AI compute is core to their product.

Google CEO Sundar Pichai announced Gemini has surpassed one billion monthly users, making it Google's fastest-growing product and the 14th to reach that milestone. The announcement coincides with a significant reorganization of Google's AI division, with Demis Hassabis stepping back and other researchers departing, while competitors have released more advanced models.

Why: Gemini's one-billion-user distribution scale means it is now a mainstream platform surface that builders should treat as a first-class integration target alongside OpenAI. The internal reorganization and researcher departures signal potential instability in Google's AI roadmap, so teams betting on Gemini APIs should track API continuity and model-version commitments rather than assume steady iteration.

Analyst Claus Aasholm estimates that Amazon, Alphabet, Meta, and Microsoft collectively hold nearly $2 trillion in purchase commitments for AI hardware and memory as of Q2 2026, with Alphabet leading at $811 billion and Apple trailing at $57 billion. A significant portion targets memory components, reflecting a shift from Apple's historical dominance in long-term component contracts to hyperscalers driving the market.

Why: If you're budgeting for GPU or AI inference costs over the next 1-2 years, this signals sustained pricing pressure and scarcity for AI hardware and memory — hyperscalers are locking up supply years ahead. Malaysian founders and developers relying on cloud AI compute should expect continued high costs for GPU-backed services and may need to weigh smaller-model or CPU-based inference strategies sooner rather than later.