Mark Russinovich, Microsoft Azure CTO tells Rust Nation UK 2025 why Azure is moving to Rust from C++

Summary

Markinovich, Microsoft's CTO and Deputy CISO, reflects on the early days of Azure and its growth from a startup-like initiative to a cornerstone of Microsoft’s cloud business. He discusses the company’s strategic shift from C++ to Rust, highlighting Rust’s security benefits, particularly in memory safety. He also explores the role of AI in driving the future of cloud computing, emphasizing that companies excelling in AI will dominate the hyperscaler space. Markinovich’s insights offer a glimpse into Microsoft’s forward-looking approach to technology, with a focus on AI, security, and scalable infrastructure.

Takeaways

• 😀 Markinovich played a key role in launching Azure at Microsoft in 2010, contributing to its technical strategy and architecture.
• 😀 In 2010, cloud computing was still an unknown concept at Microsoft, with only a small group of employees aware of Azure's existence.
• 😀 The initial development of Azure was challenging, as there was no established roadmap or software to guide its creation.
• 😀 Markinovich was optimistic about cloud computing's future but found its success deeply satisfying, particularly given Microsoft's strong position in the market.
• 😀 Microsoft is transitioning from C++ to Rust due to the security vulnerabilities in C/C++ and the advantages of Rust in terms of memory and concurrency safety.
• 😀 Rust's memory safety and secure design are critical for addressing the vulnerabilities that have historically plagued C/C++ code.
• 😀 Developers familiar with C/C++ find it challenging to transition to Rust but often become enthusiastic after overcoming the learning curve.
• 😀 Microsoft is focusing its Rust migration efforts on the most security-sensitive areas, such as older code that continues to cause vulnerabilities in Windows.
• 😀 Growth prospects for Azure are promising, with increasing demand driven by advancements in AI and the shift towards hyper-scale computing infrastructure.
• 😀 As a hyperscaler, Microsoft aims to be one of the leading winners in the AI space, recognizing that AI and hyper-scale computing are inherently linked.

Q & A

What role did Markinovich play in the development of Azure in 2010?

Markinovich was one of the key figures who helped lead the technical strategy and architecture for Azure when it was first launched in 2010. While many people contributed to Azure's development, he was there from the beginning and played a critical role in its early stages.

What was the initial reaction to cloud computing at Microsoft in 2010?

In 2010, cloud computing was a relatively unknown concept at Microsoft. The Azure team was small, and only about 200 people within the company knew what Azure was. The excitement around cloud computing was palpable, but there was also uncertainty as the technology was still in its infancy.

How did Markinovich describe the challenges of launching Azure?

Markinovich highlighted that there was no roadmap for Azure and no existing software to use as a foundation. The team had to build everything from scratch, which made the early stages of development very challenging.

Was Markinovich surprised by the success of cloud computing?

No, he was not surprised by the success of cloud computing. While pleased with its success, he had hoped from the beginning that cloud computing would be successful, especially given Microsoft's position in the market.

What is the reason behind Microsoft's move from C++ to Rust?

Microsoft is moving from C++ to Rust primarily due to security concerns. C++ has inherent vulnerabilities, and despite efforts to make it safer, it is fundamentally not designed for security. Rust, on the other hand, is designed with safety in mind, offering memory safety and concurrency safety, making it a more secure alternative.

What did Markinovich mean by 'It's not all rosy in the garden, but it's rosy enough'?

Markinovich was referring to the challenges people face when transitioning from C++ to Rust. While Rust's memory ownership and safety concepts can be difficult to grasp initially, many developers eventually experience a breakthrough and become more productive with it.

Is Microsoft planning to fully transition Azure to Rust?

Microsoft plans to move thoughtfully and gradually towards using Rust, starting with security-sensitive areas like Windows, where legacy code has resulted in vulnerabilities over the years. However, not all areas will be ported to Rust, especially those that don't involve untrusted data or high security risks.

What are the main growth prospects for Azure's business?

The growth prospects for Azure are tied to the paradigm shift driven by AI. As AI continues to grow, so does the demand for computing infrastructure. Azure, being one of the hyperscalers, stands to benefit significantly from the increasing need for AI capabilities and the associated computing power.

What is the relationship between hyperscale computing and AI according to Markinovich?

Markinovich emphasizes that hyperscale computing and AI go hand in hand. To remain competitive as a hyperscaler, a company must be adept at managing AI workloads. If a company is not excelling in AI, it risks falling behind in the hyperscale computing space.

Did Markinovich express optimism about the future of AI and Microsoft's role in it?

Yes, Markinovich expressed confidence that Microsoft would be one of the AI winners. He believes that the growth of AI and the need for hyperscale computing are inseparable, and Microsoft is well-positioned to capitalize on both trends.