Azure Application Architecture Guide

Azure Application Architecture Guide
Azure Application Architecture Guide

This manual gives a established technique for designing packages on Azure which might be scalable, secure, resilient, and fairly available. It is primarily based totally on demonstrated practices that we’ve found out from consumer engagements.


The cloud is converting how packages are designed and secured. Instead of monoliths, packages are decomposed into smaller, decentralized offerings. These offerings talk thru APIs or via way of means of the use of asynchronous messaging or eventing. Applications scale horizontally, including new times as call for requires.

These traits deliver new challenges. Application nation is distributed. Operations are performed in parallel and asynchronously. Applications ought to be resilient while screw ups occur. Malicious actors constantly goal packages. Deployments ought to be automatic and predictable. Monitoring and telemetry are important for gaining perception into the system. This manual is designed that will help you navigate those changes.

How this guide is structured

The Azure Application Architecture Guide is prepared as a chain of steps, from the structure and layout to implementation. For every step, there may be helping steering to help you with the layout of your software structure.

Architecture styles

The first choice factor is the maximum fundamental. What sort of structure are you building? It is probably a microservices structure, a greater conventional N-tier application, or a massive records solution. We have recognized numerous wonderful structure styles. There are blessings and demanding situations to each.

Learn greater: Architecture styles

Technology choices

Knowing the sort of structure you’re building, now you could begin to pick the principle generation portions for the structure. The following generation picks are critical:

  • Compute refers back to the web website hosting version for the computing sources that your programs run on. For extra information, see Choose a compute service.
  • Data shops consist of databases however additionally garage for message queues, caches, logs, and something else that an utility would possibly persist to garage. For extra information, see Choose a information store.
  • Messaging technology permit asynchronous messages among additives of the system. For extra information, see Choose a messaging service.

You will probable should make extra generation picks alongside the way, however those 3 elements (compute, information, and messaging) are imperative to maximum cloud programs and could decide many components of your design.

Design the architecture

Once you’ve got got selected the structure fashion and the essential generation components, you’re equipped to address the particular layout of your utility. Every utility is different, however the following sources permit you to alongside the way:

Reference architectures

Depending in your scenario, one in every of our reference architectures can be an awesome beginning point. Each reference structure consists of encouraged practices, at the side of issues for scalability, availability, security, resilience, and different elements of the design. Most additionally consist of a deployable answer or reference implementation.

Design principles

We have recognized 10 high-stage layout concepts so as to make your utility greater scalable, resilient, and manageable. These layout concepts observe to any structure style. Throughout the layout process, maintain those 10 high-stage layout concepts in mind. For greater information, see Design concepts.

Design patterns

Software layout styles are repeatable styles which are demonstrated to resolve particular problems. Our catalog of Cloud layout styles addresses particular demanding situations in dispensed systems. They cope with elements which include availability, resiliency, performance, and security. You can locate our catalog of design patterns here.

Best practices

Our best practices articles cowl diverse layout issues inclusive of API layout, autoscaling, statistics partitioning, caching, and so forth. Review those and practice the nice practices which are suitable to your application.

Security best practices

Our security best practices describe the way to make sure that the confidentiality, integrity, and availability of your software are not compromised via way of means of malicious actors.

Quality pillars

A a success cloud software will recognition on 5 pillars of software program quality: Cost optimization, Operational excellence, Performance efficiency, Reliability, and Security.

Leverage the Microsoft Azure Well-Architected Framework to evaluate your structure throughout those 5 pillars.

Leave a Reply

Your email address will not be published. Required fields are marked *

7 + 1 =

You May Also Like
Twelve-Factor Application of Microservices
Read More

The Twelve-Factor App

Introduction In the current era, software program is usually delivered as a service: referred to as net apps,…