The first step you need to make it done when designing a cloud application is the architecture. Choose the best architecture for the application you are building based on its complexity, type of domain, if it’s an IaaS or PaaS application, and what the application will do. Also consider the skills of the developer and DevOps teams, and if the application has an existing architecture.

Microsoft has provided the e-book version of Azure Application Architecture Guide to make the work easier. This e-book is designed to help you navigate these changes.

Traditional on-premisesModern cloud
Monolithic, centralized
Design for predictable scalability
Relational database
Strong consistency
Serial and synchronized processing
Design to avoid failures (MTBF)
Occasional big updates
Manual management
Snowflake servers
Decomposed, de-centralized
Design for elastic scale
Polyglot persistence (mix of storage technologies)
Eventual consistency
Parallel and asynchronous processing
Design for failure (MTTR)
Frequent small updates
Automated self-management
Immutable infrastructure

This guide is intended for application architects, developers, and operations teams. It’s not a how-to guide for using individual Azure services. After reading this guide, you will understand the architectural patterns and best practices to apply when building on the Azure cloud platform.

To get this free e-book, you can download it from here.