Azure Storage

This example of cloud computing system architecture diagram was created on base of the figure "Workflow to distribute workitems to pooled VMs" in the article "Azure Batch technical overview" from the Microsoft Azure website.
"Workitems workflow.
Figure 4 shows a you how to submit an application to a pool where it's distributed for processing. This uses the Batch API. ...
1. Upload input files (such as source data or images) required for a job to an Azure storage account. These files must be in the storage account so that the Batch service can access them. The Batch service loads them onto a TVM when the task runs.
2. Upload the dependent binary files to the storage account. The binary files include the program that is run by the task and the dependent assemblies. These files must also be accessed from storage and are loaded onto the TVM.
3. Create a pool of TVMs, specifying the size of the TVMs in the pool, the OS they run, and other properties. When a task runs, it is assigned a TVM from this pool.
4. Create a workitem. A job will be automatically created when you create a workitem. A workitem enables you to manage a job of tasks.
5. Add tasks to the job. Each task uses the program that you uploaded to process information from a file you uploaded.
6. Run the application and monitor the results of the output." [azure.microsoft.com/ en-us/ documentation/ articles/ batch-technical-overview/ ]
The diagram example "Workitems workflow diagram" was created using ConceptDraw PRO diagramming and vector drawing software extended with the Azure Architecture solution from the Computer and Networks area of ConceptDraw Solution Park.

This example of cloud computing system architecture diagram was redesigned from the Wikimedia Commons file: Windows Azure Network and Computes Architecture.png. [commons.wikimedia.org/ wiki/ File:Windows_ Azure_ Network_ and_ Computes_ Architecture.png]
This file is licensed under the Creative Commons Attribution-Share Alike 2.0 license. [creativecommons.org/ licenses/ by-sa/ 2.0/ ]
"Microsoft Azure (formerly Windows Azure before 25 March 2014) is a cloud computing platform and infrastructure, created by Microsoft, for building, deploying and managing applications and services through a global network of Microsoft-managed datacenters. It provides both PaaS and IaaS services and supports many different programming languages, tools and frameworks, including both Microsoft-specific and third-party software and systems." [Microsoft Azure. Wikipedia]
The diagram example "Microsoft Azure network and computes architecture" was created using ConceptDraw PRO diagramming and vector drawing software extended with the Azure Architecture solution from the Computer and Networks area of ConceptDraw Solution Park.

This Azure cloud architecture pattern diagram template was created on the base of figure in the article "External Configuration Store Pattern" from the Microsoft Developer Network (MSDN) website.
"External Configuration Store Pattern.
Move configuration information out of the application deployment package to a centralized location. This pattern can provide opportunities for easier management and control of configuration data, and for sharing configuration data across applications and application instances. ...
The majority of application runtime environments include configuration information that is held in files deployed with the application, located within the application folders. In some cases it is possible to edit these files to change the behavior of the application after it has been deployed. However, in many cases, changes to the configuration require the application to be redeployed, resulting in unacceptable downtime and additional administrative overhead. ...
Store the configuration information in external storage, and provide an interface that can be used to quickly and efficiently read and update configuration settings. The type of external store depends on the hosting and runtime environment of the application. In a cloud-hosted scenario it is typically a cloud-based storage service, but could be a hosted database or other system.
The backing store chosen for configuration information should be fronted by a suitable interface that provides consistent and easy to use access in a controlled way that enables reuse. Ideally, it should expose the information in a correctly typed and structured format. The implementation may also need to authorize users’ access in order to protect configuration data, and be flexible enough to allow multiple versions of the configuration (such as development, staging, or production, and multiple release versions of each one) to be stored." [msdn.microsoft.com/ ru-RU/ library/ dn589803.aspx]
The Azure cloud system architecture diagram template "External Configuration Store Pattern" for the ConceptDraw PRO diagramming and vector drawing software is included in the Azure Architecture solutin from the Computer and Networks area of ConceptDraw Solution Park.