SharePoint server reference architecture for public-facing website scenario

"Microsoft SharePoint is a Web application platform developed by Microsoft. First launched in 2001, SharePoint has historically been associated with intranet, content management and document management, but recent versions have significantly broader capabilities.
SharePoint comprises a multipurpose set of Web technologies backed by a common technical infrastructure. By default, SharePoint has a Microsoft Office-like interface, and it is closely integrated with the Office suite. The web tools are designed to be usable by non-technical users. SharePoint can be used to provide intranet portals, document & file management, collaboration, social networks, extranets, websites, enterprise search, and business intelligence. It also has system integration, process integration, and workflow automation capabilities.
Enterprise application software (e.g. ERP or CRM packages) often provide some SharePoint integration capability, and SharePoint also incorporates a complete development stack based on web technologies and standards-based APIs. As an application platform, SharePoint provides central management, governance, and security controls for implementation of these requirements. The SharePoint platform integrates directly into IIS - enabling bulk management, scaling, and provisioning of servers, as is often required by large organizations or cloud hosting providers." [Microsoft SharePoint. Wikipedia]
The AWS architecture diagram example "SharePoint server reference architecture for public-facing website scenario" was created using the ConceptDraw PRO diagramming and vector drawing software extended with 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 "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 DFD sample was created on the base of the figure from the NASA website. [asd-www.larc.nasa.gov/ ATBD/ DFD.html]
"Clouds and the Earth's Radiant Energy System (CERES).
EOS-Terra: Understanding Earth's Clouds and Climate.
The Clouds and the Earth's Radiant Energy System (CERES) instrument is one of several that will be flown aboard the Earth Observing System's Terra spacecraft, scheduled for launch in late1999. The data from the CERES instrument will be used to study the energy exchanged between the Sun; the Earth's atmosphere, surface and clouds; and outer space.
The CERES EOS-Terra instrument will be the second CERES instrument in Earth orbit. The first CERES instrument is currently orbiting the Earth aboard the Tropical Rainfall Measuring Mission observatory, which was launched in November 1997. Early results of the TRMM mission show that the first CERES has provided better measurement capabilities than any previous satellite instrument of its kind.
What CERES Will Measure.
CERES will measure the energy at the top of the atmosphere, as well as estimate energy levels in the atmosphere and at the Earth's surface. Using information from very high resolution cloud imaging instruments on the same spacecraft, CERES also will determine cloud properties, including cloud amount, altitude, thickness, and the size of the cloud particles. All of these measurements are critical for advancing our understanding of the Earth's total climate system and further improving climate prediction models.
The CERES instrument is based on NASA Langley's highly successful Earth Radiation Budget Experiment (ERBE) which used three satellites to provide global energy budget measurements from 1984 to 1990." [nasa.gov/ centers/ langley/ news/ factsheets/ CERES.html]
The DFD example "CERES data flow diagram" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Data Flow Diagrams solution from the Software Development area of ConceptDraw Solution Park.