Cloud Native 4 min read

Translation of 32 Cloud Design Patterns for Cloud‑Native Applications

This article presents a Chinese translation of 32 cloud design patterns originally documented by the Azure cloud team, explaining how these patterns—covering availability, data management, security, scalability, and more—can guide enterprises in migrating monolithic applications to cloud‑native architectures across any major cloud provider.

DevOps
DevOps
DevOps
Translation of 32 Cloud Design Patterns for Cloud‑Native Applications

With rapid technological development, application architectures have evolved from monolithic, layered, and SOA models toward microservices, while infrastructure has shifted from mainframes and self‑built data centers to services hosted on cloud platforms. All of this aims to launch web and mobile applications faster and more securely, providing high scalability, elasticity, and self‑recovery from both architectural and infrastructural perspectives.

Microservices give applications architectural scalability and are well suited to run on cloud‑provided VMs or containers, while programmable interfaces of cloud services make infrastructure automation exceptionally easy, facilitating the adoption of DevOps. Cloud adoption by enterprises has become an irreversible trend.

However, because of the large number of legacy systems, directly porting enterprise applications to the cloud without modification is often impractical. Although we can apply microservice decomposition strategies—based on functionality, data, DDD principles, etc.—to make applications more cloud‑ready, many challenges still arise during actual implementation.

The Azure cloud computing team has summarized cloud design patterns from the perspectives of availability, data management, design and implementation, messaging, management and monitoring, performance and scalability, resilience, and security, offering practical patterns and case studies for enterprise cloud migration. Although the examples use Azure services, readers can apply the same patterns with other providers such as AWS, GCP, or Huawei Cloud to smooth the migration process.

Coincidentally, my colleagues and I are also researching Cloud‑Native technologies, and we spent a weekend translating these 32 cloud design patterns. Our translation is limited by time and skill, so we apologize for any issues; please feel free to open an issue or submit a PR on GitHub, which we greatly appreciate.

Note: During translation we discovered that some of the cloud design patterns had already been partially translated three years ago, but the coverage was incomplete and readability was average, so we decided to complete the translation.

Feedback and Contribution

Please create the corresponding issue on GitHub to report problems.

Contributors

iambowen@github

boweniam@twitter

@tongzh

@wldandan

gitbook address:

https://iambowen.gitbooks.io/cloud-design-pattern/content/

Click the original link to view the full translation.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

Design Patternscloud migrationcloud-nativeMicroservices
DevOps
Written by

DevOps

Share premium content and events on trends, applications, and practices in development efficiency, AI and related technologies. The IDCF International DevOps Coach Federation trains end‑to‑end development‑efficiency talent, linking high‑performance organizations and individuals to achieve excellence.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.