External configuration store pattern

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.

This IVR diagram sample illustrates how ENUM works by giving an example: Subscriber A sets out to call Subscriber B:
1. The User Agent of an ENUM-enabled subscriber terminal device, or a PBX, or a Gateway, translates the request for the number +34 98 765 4321 in accordance with the rule described in RFC 3761 into the ENUM domain 1.2.3.4.5.6.7.8.9.4.3.e164.arpa.
2. A request is sent to the Domain Name System (DNS) asking it to look up the ENUM domain 1.2.3.4.5.6.7.8.9.4.3.e164.arpa.
3. The query returns a result in the form of so called Naming Authority Pointer Resource NAPTR records, as per RFC 3403. In the example above, the response is an address that can be reached in the Internet using the VoIP protocol, SIP per RFC 3261.
4. The terminal application now sets up a communication link, and the call is routed via the Internet.
This IVR diagram sample was designed on the base of the Wikimedia Commons file: Ejemplo ENUM.jpg. [commons.wikimedia.org/ wiki/ File:Ejemplo_ ENUM.jpg]
"Being able to dial telephone numbers the way customers have come to expect is considered crucial for the convergence of classic telephone service (PSTN) and Internet telephony (Voice over IP, VoIP), and for the development of new IP multimedia services. The problem of a single universal personal identifier for multiple communication services can be solved with different approaches. One simple approach is the Electronic Number Mapping System (ENUM), developed by the IETF, using existing E.164 telephone numbers, protocols and infrastructure to indirectly access different services available under a single personal identifier. ENUM also permits connecting the IP world to the telephone system in a seamless manner." [Telephone number mapping. Wikipedia]
The IVR diagram example "Example ENUM" was designed using ConceptDraw PRO diagramming and vector drawing software extended with the Interactive Voice Response Diagrams solution from the Computer and Networks area of ConceptDraw Solution Park.

The vector stencils library "AWS Database" contains 30 Amazon Web Services database icons: Amazon DynamoDB icons, Amazon ElastiCache icons, Amazon Relational Database Service icons, Amazon Redshift icons, AWS Database Migration Service icons.
Use it to draw Amazon Web Services architecture diagrams with ConceptDraw PRO diagramming and vector drawing software.
"Amazon DynamoDB is a fast and flexible NoSQL database service... It is a fully managed cloud database and supports both document and key-value store models." [aws.amazon.com/ dynamodb/ ]
"ElastiCache is a web service that makes it easy to deploy, operate, and scale an in-memory cache in the cloud." [aws.amazon.com/ elasticache/ ]
"Amazon Relational Database Service (Amazon RDS) makes it easy to set up, operate, and scale a relational database in the cloud. ... Amazon RDS provides you six familiar database engines to choose from, including Amazon Aurora, Oracle, Microsoft SQL Server, PostgreSQL, MySQL and MariaDB." [aws.amazon.com/ rds/ ]
"Amazon Redshift is a fast, fully managed, petabyte-scale data warehouse that makes it simple and cost-effective to analyze all your data using your existing business intelligence tools." [aws.amazon.com/ redshift/ ]
"AWS Database Migration Service helps you migrate databases to AWS easily and securely." [aws.amazon.com/ dms/ ]
The AWS icons example "Design elements - AWS Database" is included in the AWS Architecture Diagrams 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 "Health Endpoint Monitoring Pattern" from the Microsoft Developer Network (MSDN) website.
"Health Endpoint Monitoring Pattern.
Implement functional checks within an application that external tools can access through exposed endpoints at regular intervals. This pattern can help to verify that applications and services are performing correctly. ...
It is good practice—and often a business requirement—to monitor web applications, and middle-tier and shared services, to ensure that they are available and performing correctly. However, it is more difficult to monitor services running in the cloud than it is to monitor on-premises services. ...
Implement health monitoring by sending requests to an endpoint on the application. The application should perform the necessary checks, and return an indication of its status.
A health monitoring check typically combines two factors: the checks (if any) performed by the application or service in response to the request to the health verification endpoint, and analysis of the result by the tool or framework that is performing the health verification check. The response code indicates the status of the application and, optionally, any components or services it uses. The latency or response time check is performed by the monitoring tool or framework." [msdn.microsoft.com/ ru-RU/ library/ dn589789.aspx]
The Azure cloud system architecture diagram template "Health endpoint monitoring 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.