Innovate with cloud-native apps and open source on Azure

Regular Contributor

This article was originally published as part of Microsoft Ignite 2021

 

Written by Brendan Burns, Corporate Vice President, Azure Compute

 

Welcome to Microsoft Ignite. Today, I'm sharing how Microsoft is empowering you to innovate with cloud-native and open source on Azure.

 

The growth of Kubernetes and cloud-native applications in Azure and the broader technology has been nothing short of humbling and awe-inspiring. Open innovation is at the heart of nearly every innovation in cloud computing. The cloud-native ecosystem empowers people to build applications that make it easy to take advantage of this innovation. It’s no surprise that according to IDC, more than 90 percent of new apps will be cloud-native by 2025.1

 

Using cloud-native design patterns helps many of our customers achieve the agility, reliability, scalability, and security demanded by the next generation of applications. Obviously, over the last few years, the healthcare industry has needed to adapt and deploy new applications rapidly. When New South Wales Health Pathology needed a scalable, flexible, and secure solution for statewide health diagnostics information, they chose Azure Kubernetes Service (AKS), Azure Functions, Azure IoT Hub, and Azure Cosmos DB to implement a large-scale digital health platform. But healthcare isn’t the only mission-critical service that relies on Azure Kubernetes for agility, scale, and reliability. Every day, more than one million travelers rely on the timely services of ÖBB—Austrian Federal Railways—Austria’s largest mobility services provider. They migrated Ticketshop, their ticket issuing platform, to run on containers on Azure Kubernetes Service and migrated some 11 TB of data from on-premises Oracle servers to Azure Database for PostgreSQL. For me, the most thrilling part of this migration is that the increased automation in AKS freed up their engineers from the toil of keeping an eye on infrastructure and instead enabled them to focus on the development of their service (and, of course, even more automation).

 

Read the full article

0 Replies