Azure Architecture

The Azure Architecture solution contains 21 examples and 18 libraries containing 739 vector graphics and objects.

Design Elements Azure Architecture — Cloud

Design Elements Azure Architecture — Enterprise

Design Elements Azure Architecture — Microsoft Products

Design Elements Azure Architecture — Symbols

Design Elements Azure Architecture — Virtual Machines

Related News:

Meet the New Version of Azure Architecture Solution

Examples

There are a few samples that you see on this page which were created in the ConceptDraw DIAGRAM application by using the Azure Architecture solution. Some of the solution's capabilities as well as the professional results which you can achieve are all demonstrated here on this page.

All source documents are vector graphic documents which are always available for modifying, reviewing and/or converting to many different formats, such as MS PowerPoint, PDF file, MS Visio, and many other graphic ones from the ConceptDraw Solution Park or ConceptDraw STORE. The Azure Architecture solution is available to all ConceptDraw DIAGRAM users to get installed and used while working in the ConceptDraw DIAGRAM diagramming and drawing software.

Example 1: Push Notification Lifecycle Overview

This diagram was created in ConceptDraw DIAGRAM using the combination of libraries from the Azure Architecture solution. An experienced user spent 15 minutes creating this sample.

The push notifications are widespread on mobile devices, for Windows are first introduced at Win 8. They are the best at the cases of orientation on specific users with personalized content. From the cloud to your Windows Store applications the notifications can be sent with help of Windows Push Notification Services (WNS), even at the case when your application is not running at the moment. This sample shows the overall overview of the push notifications lifecycle via Windows Azure Notification Service (WNS). The offered diagram is an example of the sort of process you can set up using the Microsoft Azure platform and Windows Azure Mobile Services, the main goal of which is to make easier for developers the process of adding the cloud backend to the client applications under Windows 8, Windows Phone, iOS and Android. The diagram shows the relationship between Azure cloud and Windows 8 application, each of three steps is clearly annotated: Request Channel URL, Register With your Cloud Service, Authenticate and Push Notification.

Example 2: Grid Computing System Architecture

This diagram was created in ConceptDraw DIAGRAM using the combination of libraries from the Azure Architecture solution. An experienced user spent 10 minutes creating this sample.

At the use of powerful ConceptDraw DIAGRAM means you can create simple and effective diagrams in a matter of moments. All icons at the Azure Architecture solution libraries are scalable and professionally drawn. This diagram illustrates the architecture of the grid computing system, which connects many personal computers via the Internet with using the inter-process network communication (IPC). Such type of communications as the IPC is an activity of exchanging the data between multiple and commonly specialized processes with using the communication protocols. In applications that use the IPC the clients make requests of data and the server responds to these requests. The grid computing is the set of computer resources from the different locations, which strive to achieve a common goal, at this all grid computers are used to perform different tasks or applications. The grid can be considered as a distributed system with non-interactive workloads, which include large quantity of files.

Example 3: Microsoft Azure Network and Computes Architecture

This diagram was created in ConceptDraw DIAGRAM using the combination of libraries from the Azure Architecture solution. An experienced user spent 10 minutes creating this sample.

Windows Azure cloud computing platform and infrastructure is effectively used for development, deployment and management varied services and applications across the global network of datacenters that are managed by Microsoft Corporation. This diagram sample illustrates the Microsoft Azure Network, Azure services for computing and computes architecture, depicts how the data are transferred and stored. It is a simple process to create with help of ConceptDraw DIAGRAM software and its extensive drawing tools any effective and clear illustrations, which can be easily understood by all stakeholders. The clarity of narration the information, as well the brightness are the distinctive characteristics of this illustration. When creating Azure Architecture diagrams do not forget about such important component as a visual perception, with help of color any diagram can be vivified, the color is able to make it interesting for all and everyone, it helps to highlight the key points and to set the accents.

Example 4: Windows Azure Reference Architecture

This diagram was created in ConceptDraw DIAGRAM using the combination of libraries from the Azure Architecture solution. An experienced user spent 15 minutes creating this sample.

The ConceptDraw Solution Park amazes us with amount of multifarious solutions for solving different types of tasks. Once again the ConceptDraw Solution Park provides a solution with a rich selection of ready-to-use vector stencil symbols, pictograms and other design elements, which allow you to furnish your diagrams with professional symbols relating to Azure services and Azure Architecture. This Cloud computing system architecture diagram depicts the architectural overview of developer and infrastructure services that are currently available in Windows Azure. This reference architecture is represented in a layered form, division on four layers (Client Layer, Integration Layer, Application Layer, Data Layer) is quite visual, especially at the use of different colors. Based on the picture from the "Windows Azure Solution Cookbook" post published at the Clint Edmonson's blog on notsotrivial.net website, this sample was designed in seconds with powerful drawing tools of ConceptDraw DIAGRAM diagramming software and Azure Architecture solution.

Example 5: Workitems Workflow Diagram

This diagram was created in ConceptDraw DIAGRAM using the combination of libraries from the Azure Architecture solution. An experienced user spent 20 minutes creating this sample.

The Microsoft Azure Cloud platform allows the users to set up multiple instances of virtual machines. The understanding their relationships and access states can be confusing - luckily the Azure Architecture solution provides you with tools and templates you need to make the job a breeze. This diagram example demonstrates the workflow of distribution the workitems to pooled VMs, shows how to submit an application to pool, where it is then distributed for processing using the Batch API. The represented workflow includes six steps: uploading of input files required for working with Azure storage account; uploading of dependent binary files to the storage account; creation of a Batch pool of virtual machines that will execute your tasks, specifying their size, the OS they run, and other parameters; creation of a workitem that enables to manage a job of tasks; adding the tasks to the job; running the application and monitoring the output results.

Example 6: Microsoft Azure StorSimple Architecture

This diagram was created in ConceptDraw DIAGRAM using the combination of libraries from the Azure Architecture solution. An experienced user spent 20 minutes creating this sample.

Microsoft Azure StorSimple is a feature developed by Microsoft Corporation for Azure platform, which lets to extend the local StorSimple storage of an enterprise with Azure. In other words, the Microsoft Azure StorSimple is an integrated storage solution that manages the tasks of storage on the local devices and in Microsoft Azure cloud storage. The easily manageable Microsoft Azure StorSimple solution helps effectively exclude a lot of problems and costs that are associated with enterprise storage and data protection, and lets IT departments to guarantee their users the ability to store the large amounts of information in a very short time. This System architecture diagram was made on the base of picture from the Microsoft Azure website attached to the "What is StorSimple?" article of Sharon Smith. It illustrates in details the work of Microsoft Azure StorSimple solution, the involved devices and the processes that take place at this.

Azure Architecture Template 1: Competing Consumers Pattern

This diagram was created in ConceptDraw DIAGRAM using the combination of libraries from the Azure Architecture solution. An experienced user spent 10 minutes creating this sample.

This sample visual diagram represents the Competing Consumers Pattern that was created on the base of figure offered at MSDN website. In its designing were used not many elements, the range of vector design symbols available at the libraries of Azure Architecture solution is a lot more, it significantly extends your opportunities and abilities in drawing both complex and simple diagrams. The applications that run in a cloud can process the requests, which come in a form of messages. For realization the communication channel between the application and the instances of the consumer service is used a message queue, the consumer service instances receive the messages from the queue and process them. This sample illustrates how useful is the possibility to process synchronously multiple messages that are received on the same messaging channel, this allows the system to optimize the throughput, to enhance the availability and scalability, as well as to distribute the workload.

Azure Architecture Template 2: External Configuration Store Pattern

This diagram was created in ConceptDraw DIAGRAM using the combination of libraries from the Azure Architecture solution. An experienced user spent 10 minutes creating this sample.

This sample was designed to demonstrate the External Configuration Store Pattern that is one of numerous patterns offered by Microsoft Developer Network (MSDN) website. The application runtime environment usually contains the configuration information. It is effective way to store the configuration information in external storage, which can be of different types depending on the hosting and runtime environment of application. At this, it is needed to ensure the interface convenient for quick and efficient reading and updating the configuration settings. As for the cloud system, it is usually used a cloud-based storage service, but also may be used a hosted database or other system. This template provides opportunities for simplifying the management and control the configuration of data, for exchanging the configuration of data through the applications and application instances. The external configuration store is the main element on this diagram. Besides, this pattern is also incredibly useful for managing multiple applications.

Azure Architecture Template 3: Health Endpoint Monitoring Pattern

This diagram was created in ConceptDraw DIAGRAM using the combination of libraries from the Azure Architecture solution. An experienced user spent 20 minutes creating this sample.

This Health Endpoint Monitoring pattern is based on the official data from the Microsoft Developer Network (MSDN) website and can serve in its turn the good base for designing other professional looking Azure cloud architecture diagrams and infographics. The monitoring of web applications availability and the correctness of their performance is in many cases one of the main business requirements, at this the monitoring of on-premises services is more easiest task than services running in a cloud. The endpoints allow to monitor the application and to interact with it. This pattern helps in verification the correctness of work of applications and services, and illustrates the scheme of implementation the health monitoring by sending requests to the endpoint on the application. After making the necessary checks, the application returns an indication of its status. Besides, the health monitoring includes also analysis of results by the framework or monitoring tool that executes the health verification check.

Azure Architecture Template 4: Scheduler Agent Supervisor Pattern

This diagram was created in ConceptDraw DIAGRAM using the combination of libraries from the Azure Architecture solution. An experienced user spent 10 minutes creating this sample.

The Azure Architecture template is an example of a pattern representing the Scheduler, Agent and Supervisor logical components, which manage the steps of work to be executed as a part of overall process or task. The Scheduler organizes and runs the steps from which consists the overall task that will be performed, also maintains the status (started, completed) of each step in the State Store. The Agent accesses to the Remote service or Remote resource and obligatory includes the error handling and retry logic. The Supervisor is responsible for monitoring and for updating the statuses of the steps at the State Store, the failed steps must to be reattempted by the Scheduler. This Azure Architecture template is quite simple, but you can always expand it and update with additional information, comments and also with data, because in a real implementation you can have many instances of the Scheduler running simultaneously.

Azure Architecture Template 5: Valet Key Pattern

This diagram was created in ConceptDraw DIAGRAM using the combination of libraries from the Azure Architecture solution. An experienced user spent 10 minutes creating this sample.

In applications, which use the cloud-hosted storage systems or queues is useful and commonly applied the restriction of access with help of key or token, usually referred to as a valet key. This way lets to maximize the scalability and performance, to offload the data transfer operations and to minimize the cost. The key or token lets effectively solve the problem of control the access to the data stores, is used for restriction the access to specific resources, files or services and needs to be validated before opening the access. This Azure cloud architecture pattern demonstrates a work with a key token, the step-by-step process of key obtaining and applying, which includes the user's request, its checking for validity, the generation of a key token, its return for user and in result the getting of access to target resource. The colorful and vivid diagrams are always in a winning position at the presentations and reports.

More Examples and Templates

Design Elements — Azure Architecture — Clouds
Design Elements — Azure Architecture — Communications
Design Elements — Azure Architecture — Concepts

Design Elements — Azure Architecture — Databases
Design Elements — Azure Architecture — Deprecated
Design Elements — Azure Architecture — Devices

Design Elements — Azure Architecture — Intune
Design Elements — Azure Architecture — Operations Management Suite
Design Elements — Azure Architecture — Security

Design Elements — Azure Architecture — Operations Manager
Design Elements — Azure Architecture — Servers
Design Elements — Azure Architecture — Sites
Design Elements — Azure Architecture — Users

Digital Marketing Using Azure Database for MySQL
Retail and E-Commerce Using Azure-Database for PostgreSQL
Solution Architecture — SAP on Azure

SQL Azure Client Access Architecture
Windows Azure Computes and Management Architecture
Backends for Frontends Pattern Template

Cache — Aside Pattern
Command and Query Responsibility Segregation (CQRS) Pattern
Event Sourcing Pattern
Gateway Offloading Pattern