Distributed System Design suite

Abstract:Microsoft Visual Studio 2005 team edition is a graphical design tool suite provided with Visual Studio 2005, mainly for architects and developers. It supports visual design and verification of the Connection System. Visual Studio 2005 team edition for Software Distributed ts is an early product of the Dynamic System Management Plan (DSI), designed to improve the design, deployment, and management of enterprise-level distributed systems.

NoteThis article was originally published on. Net developer's journalJanuary 2005. The publisher's license is reproduced here.

Content on this page

	Objective: To design a visual connection system
	Design objective: To design the operation
	Visual Studio 2005 team edition for software development ts "distributed design suite"

Objective: To design a visual connection system

The service-oriented architecture or "Connection System" architecture is the next generation of distributed applications.Program. The Microsoft indigo platform provides industry-leading service-oriented application implementation. Indigo will be built on the soap and web services supported by today's Windows platforms. It adds extensive support for transmission and application topology, enabling secure, reliable, and persistent message-based communication between services. Although the release of indigo technology is just around the corner, you can use soap, XML Message Processing, and web services to build service-oriented applications. Web Services provide special methods for integrating heterogeneous information systems. To do this, wrap the autonomous system behind the infrastructure of the public web service, so that you can access it through multiple devices (internal and external of the Enterprise Firewall. Web Services provide powerful support for edge systems, so as to implement new business processing that utilizes existing system resources. In addition, it provides the possibility to increase the usage rate in the new system structure. It is increasingly difficult to visualize the application structure as a whole, because the structure is more trivial in the service-oriented architecture. It is also important to emphasize the interface design provided by the Service. To enable interoperability, these interfaces must be message-based. It is important to design new messages and ensure they comply with the existing message architecture. In a service-oriented architecture, it is increasingly important to help application architects and designers visualize and design applications as a whole.

Back to Top

Design objective: To design the operation

Whether distributed or not, all applications require services on the underlying platform. Generally, developers are responsible for the Configuration Requirements of "record/specify" Application Service dependencies and target deployment environments. Although many development tools only focus on the functional requirements of applications, non-functional requirements are usually the root cause of configuration and/or deployment problems. On the other hand, the operating and it institutions have different development tools to cater to the non-functional aspects of distributed systems, while focusing on network and infrastructure design, performance monitoring and management. The actual problem is that the operator view is part of the application, while the developer view is part of the infrastructure. It is exactly this information that needs to be captured and communicated between the two groups. Consider developing and deploying ASP. NET web services. Although the primary goal of developers is to implement services, they always need to care about security and identity authentication models. They must also consider which other support services are required in the target environment, and which parts of the Runtime Library configuration can enable the Web service to operate as needed. The operator needs to understand the protocols and services required by the new service and whether they comply with the company's IT strategy. If you leave this link, deployment problems may occur, resulting in configuration mismatch. Worse, it will lead to design and data center inconsistencies, resulting in a large amount of IT budget consumption on low-quality overhead. While many organizations try to solve communication problems through documents, design comments, and detailed charts, What they lack is actually tools and public languages that can effectively implement and communicate strategies. In addition, these processes have been removed from the actual tools used by developers and operators on a daily basis to expose the problems of the process itself. These groups are separated in terms of organization and function. They seldom collaborate in advance, usually by instinctively diagnosing problems that can be avoided early in the development process. Visual Studio 2005 team edition for software development ts is a unified development environment that brings these two groups into the software development cycle and gradually fills the gap between them.

Back to Top

Visual Studio 2005 team edition for software development ts "distributed design suite"

To provide an integrated design experience to achieve the goal of "visual design and verification of the Connection System", the design suite of the tool uses the system-defined model (SDM) in the dynamic system management plan (DSI) it is built on the basis of the underlying metadata model. This not only serves applications, but also describes the concept of connectivity, configuration, and relationship for the runtime environment. SDM is based on multi-layer models (applications, application host environments, network topologies, operating systems, and physical devices ). Therefore, these tools can now express relationships based on requirements and policies across all layers of the distributed system. Visual Studio 2005 team edition for software development ts is also designed as an extensible platform to provide professional knowledge in the application field (Web Services, web applications, data access, etc) internal and external cooperation. This does not cover the operating field (runtime host environment, security, connectivity, and configuration ). Therefore, they can define their own abstractions.

Integrate two areas (development and operations) into one toolkit so that Microsoft can solve these customer problems in the following ways:

•	Use the common language (SDM) to describe the design and configuration of the entire distributed system.
•	Abstract is used so that developers and architects in various fields can communicate with each other based on commonalities.
•	Allows architects or developers to express application requirements for running the library environment.
•	Allow the operator (or the application architect who understands the requirements of the target deployment environment) to express the application Runtime Library, security, and connection requirements that are aligned with the policies of the target deployment environment.
•	Integrates with the existing Visual Studio project system and. NET platform technology.
•	And Visual Studio team system products andSource codeControl functions are integrated.
•	The policy is positioned in DSI planning to enable deployment and management solutions and support indigo in future Visual Studio 2005 team edition for software release ts.
•	Build an isV and partner ecosystem using a scalable platform.

Design Kit features

the Application Designer (AD) provides a design surface for chart applications that publish services and communicate over messages. Users can describe these messages through the communication endpoint. This can be done using SOA protocol (such as soap) through the operation method or the method based on the WSDL protocol message. Before writing Code , You can visually connect to the application design through the communication dependencies exposed by the endpoints in the Image Layout. Therefore, applications in this context are autonomous deployment units (such as web applications and Windows applications) that run in their own process spaces ). Therefore, in the solution, chart visualization does not include dependency assembly or project reference (by definition, it is not an "application "). Applications implemented from charts through user operations generate the initial implementation of project structures and agreements. They are then fully integrated with Visual Studio projects and language systems. They are always synchronized with the design surface and provide users with options to edit on the design surface or in the code editor. Visual Studio 2005 team effecect supports Web Services, web applications, Windows applications, external databases, external web services, and external BizTalk services. Ad is also used to capture application configurations that are fully synchronized by the designer (for example, Web. config and web application configurations from IIS ). This allows architects or developers to capture the exact configurations required by the application and expose rich metadata to the constraint engine (hidden part of the tool. Therefore, other designers in the suite can use this information to perform Constraints Verification and consistency checks, and generate deployment information (see system designer, Logical Data Center designer, and deployment designer later ).

the architect uses the Logical Data Center designer (LDD) to create a chart that represents a certain logical structure of the data center. In this way, important information about the target deployment environment in a specific application field can be conveyed to developers. Capture this information in the tool to verify the design and Configuration Requirements of the application (see the deployment designer later) to improve the possibility of successful deployment. The chart itself indicates the abstraction of the actual environment. According to the design, it does not capture the typical "infrastructure or system architecture" elements (such as firewalls, routers, switches, IP addresses, and so on ). These are usually part of the communication problem between the operation group and the Development Group. On the contrary, charts mainly focus on capturing the host environment of the application program library to the design element named "logical server. The information specified in this chart indicates the allowed communication type, enabled service type, and Configuration Requirements for the host environment that affects application design and runtime characteristics. LDD allows architects to specify charts that interconnect logical servers to specify and/or import actual server settings. You can also specify the topology of a data center by indicating the application host environment with specific protocols (such as Web server, database server, application server, security zone, and communication path. After describing the Logical Data Center, you can start to specify policy constraints for the application. These applications will host in this data center representation. For example, with this chart, the architect can specify ASP. Net Security Requirements for Web applications hosted on a specific IIS web site. You can specify the connectivity to other logic servers (such as databases and Windows Services. Users can also define logical boundaries (called "zones") that represent security, communication, or other physical barriers. application developers will find it useful when considering distributed design. Similar to the requirements that application architects can specify a host for LD configuration in AD, the infrastructure or operation architect can also specify application requirements for ad application configuration.

To create a connection system, the application architect uses the system designer (SD) to visualize and build the applications defined in the ad. The configured system includes one or more applications configured for the specific deployment of the system. A system can contain (nested) Other systems; therefore, it allows visualization and the designation of a large service-oriented architecture. Through the system designer, the application architect can describe the dependencies on the services provided by other systems without having to know the internal structure of the applications that constitute the system in advance. The system designer provides a top-down design mode. The system can be built at a higher level and then visualize and define a single application in the system (if the application in the system is part of the solution. It can also encapsulate Services exposed by applications in the system. In particular, architects can choose which services can be directly solved outside the system. The system designer can be used to solve EAI and edge systems (in which existing applications publish services through web service protocols ).

The architect uses the deployment designer (dd) to create the deployment configurations of the configured system. This is done by verifying the logical expression of the data center (LDD. Next, generate the deployment configuration (called the deployment Report) and use it to communicate with developers and write deployment scripts. Dd provides a graphical binding experience from the system diagram to the Logical Data Center diagram, and provides visual feedback. This is done when the requirements of the configured system comply with the specifications required by the data center. Verification feedback is executed at multiple levels, such as communication paths, protocols, specific configurations of the data center environment, and application configuration requirements. Visual Studio task list integration provides a simple navigation mechanism to highlight relationship graphs (AD, SD, and/or LDD ). It can also help users select systems that conflict with data center policies. It also provides users with the ability to correct configuration errors before deployment and before implementation. The navigation function also allows you to view the source of the constraint definition for further exploration of problem domains. This dd is the main communication mechanism used to visualize how to deploy the configured system to a similar data center environment. The deployment report can be generated from the design surface, and you can specify options to generate a readable (HTML) report. The report will contain the relationship diagram and deployment data. Deployment data includes configuration settings for each application and Logic Server, and the list of files to be deployed.

Visual Studio 2005 team EditionScalable platform

Visual Studio 2005 team edition is designed as an extensible platform to enable third parties to leverage existing expertise while leveraging the visual design and verification features of the distributed system design suite. This is the first version that follows a completely unified development environment (as part of the Visual Studio team system) for planning. The scalability provided by Visual Studio 2005 allows third parties to record and build various aspects of a distributed system for more complete application Definitions. The scalability allows third parties or ISVs to create their own applications or Logic Server types. This is accomplished by communication requirements, Host Requirements, configuration settings, and constraints. These new types can be easily added to the design surface and integrated with the native design elements provided in the first version. Metadata collected in the design experience can be used to constrain specifications and output in deployment reports. Visual Studio 2005 does not allow you to integrate and synchronize configurations and manually written code to the Project systems of these new design elements. However, this feature will be added to later versions of the tool suite.

Link

•	Duration20MinutesMsdn TV, Overview"Visual Studio team effecect"
•	Visual Studio 2005 team system: designing distributed systems for deployment
•	Visual Studio 2005 team edition for software release TS(Located inMsdn)