The author argues that despite improvements in open-weight models, most AI inference will remain in datacenters because local models can't match frontier performance and are actually more expensive to run. Batching hundreds of users' requests together and specialized datacenter GPUs make cloud inference roughly 30x more efficient than running models at home, and users will always prefer the strongest available model in their budget.

• Datacenter inference beats local by ~30x on efficiency due to request batching and specialized GPUs (e.g., B200 vs RTX 4090)
• A home GPU rig's upfront cost plus $50-300/month in power outweighs just paying for years of API access
• Users always gravitate to the strongest model they can afford, so smaller local models keep losing ground even as they improve
• Local models will persist only in niches like low-latency voice interfaces, privacy-focused use, or unreliable internet—not as the dominant paradigm

Amazon’s contract with Anthropic will move to per-token billing next year, threatening a steep spike in costs for services like Kiro, Quick and Alexa Shopping that use Claude. To curb expenses, Amazon is exploring OpenAI’s models. Meanwhile, Anthropic is deepening ties with Google Cloud and a recent security dispute has driven a wedge between the two.

• Anthropic's shift to per-token billing next year threatens to spike Amazon's costs for Claude-dependent tools like Kiro, Quick, and Alexa Shopping, pushing Amazon to explore OpenAI as an alternative.
• Amazon's OpenAI commitment ($50 billion) now dwarfs its Anthropic investment (grown from $4 billion to a possible $33 billion), signaling a strategic pivot.
• Anthropic is hedging its own bets by committing $200 billion to Google Cloud over five years, making Google a second major infrastructure partner.
• Amazon triggered a government shutdown order against Anthropic's Fable 5 and Mythos 5 models over alleged cyberattack-enabling data, a move that coincided suspiciously with Amazon's own security-AI launch.

This issue covers SpaceX’s $6.3 billion deal with Reflection AI to open Project Colossus compute access and OpenAI’s launch of GPT-5.5 Cyber security tools via its Daybreak partner program. It also highlights Alibaba’s HappyHorse video model, Anthropic’s encrypted reasoning in Claude Code, and advances in agentic and open-source AI models.

• SpaceX is betting $6.3B on Reflection AI to rent out Project Colossus's Nvidia GB300 compute for training open-source models, showing even space companies now see AI infrastructure as a core business.
• OpenAI is restricting GPT-5.5-Cyber to a limited release embedded through partner products (Daybreak) rather than opening broad access, prioritizing controlled security use over democratized availability.
• Loop engineering is emerging as a shift from one-off prompting to autonomous agents that select tasks, execute, verify, and iterate on their own.
• Small specialized models are closing the gap with frontier systems—Moebius (0.22B params) matches larger inpainting models at 15x the speed, and "knowledge agents" let smaller LLMs compete via embedded domain data.

Microsoft will invest A$25 billion (US$18 billion) by 2029 to expand Australia’s digital infrastructure, AI supercomputing capabilities and cloud capacity. The move aims to boost commercial cloud services and AI/GPU offerings for local customers.

• Microsoft is investing A$25 billion (~US$18 billion) into Australia by 2029, its largest-ever single investment there
• Funds will expand data centers, Azure cloud capacity, and AI/GPU supercomputing infrastructure across multiple states, adding to existing NSW and Victoria facilities
• Aims to cut latency, meet data-sovereignty requirements, and give local finance, mining, government, and healthcare sectors faster access to Azure AI tools and OpenAI models
• Includes partnerships with universities and research institutes to build AI talent and drive commercial R&D

In this Pragmatic Engineer episode, Martin Kleppmann walks through updates in the second edition of Designing Data-Intensive Applications and shares how his LinkedIn experience shaped the book’s core concepts. He breaks down trade-offs in multi-region and cloud architectures, explains why replication still matters more than sharding, and predicts a rise in formal verification and local-first software.

• Second edition of DDIA cuts MapReduce coverage in favor of Spark and Flink, reflecting how the field has moved on
• Manual sharding has become rare thanks to bigger hardware and managed services, making replication the fault-tolerance skill every team now needs
• Kleppmann predicts LLMs will make formal verification mainstream by automating proof generation, shifting the bottleneck to human review
• Architecture decisions like multi-region or multi-cloud are business trade-offs between risk and cost, not universal best practices

This article explores the evolving role of data engineers over the past 50 years, highlighting their often unnoticed contributions to data infrastructure. It discusses the challenges they face, such as managing dependencies and schema changes, while emphasizing that the core problems remain unchanged despite new tools and technologies.

• The core problems of data engineering—dependencies, integration issues, schema changes—haven't changed in 50 years despite new tools like dbt, Iceberg, and cloud warehouses.
• Data engineers are invisible when things work but instantly blamed when something breaks.
• Real-time data requests are often unjustified since almost no one can explain how a 10-minute delay would actually change a decision.
• Industry growth reflects better marketing and rebranded terminology more than genuine advances in solving data management problems.