.NET platform architecture
The entire .NET platform architecture can be divided into 4 main parts:
.NET Infrastructure and Tools: Used and running infrastructure and tools for electronic enterprise systems, including Visual Studio.net, .NET Enterprise Servers, .NET Framework. .NET Basics: .NET services include a set of information shared services for Internet, such as Passport.NET (for user authentication), and services for file storage, user preference management, calendar management. These services will be provided by Microsoft and Microsoft partners. .NET user experience: This will be a wider, more adaptable user experience, information can be provided in a variety of different devices.
.NET device: This device software makes it possible to use a new smart Internet device that can utilize network services. [Jm1]
.NET Framework and Visual Studio.net
Perhaps the most important part of the .NET platform is .NET Framework. This is a comprehensive operating environment closely related to the operating system. It includes a component-oriented intermediate layer infrastructure (COM ), a Common Language Runtime (CLR) environment, a quarantine compiler, a set of operating system libraries that packages the .NET component model. The .NET system (may not include the data layer, the author will discuss each layer of the server side in the interoperability) The operating system of the server side will run. NET FRAMEWORK.
Closely related to .NET Framework is the main programmer development tool, Visual Studio.net. Indicates that the layer programmer uses Visual Studio.net to define logic to submit the HTML page to the thin client system. Business Layer Programmer uses Visual Studio.net to implement business logic in multiple languages, and then package business logic as COM components.
Visual Studio.net is a neutral language. It is considered to be the best open programming platform that can insert multiple languages. The "Standard" Microsoft language that can be used with Visual Studio .NET by VisualBasic, Visualc and Visualc #. Other languages can be obtained through third parties, including Fujitsu's COBOL languages, Interactive Software Engineering's Eiffel Language. Many other languages are compatible with Visual Studio, including Haskell, Mercury, Oberon and Perl are under research on university research.
Visual Studio.NET (actually, it is the entire .NET platform) language neutral to the .NET platform policy is critical. It is achieved by translating all Visual Studio.NET languages into a universal language called Intermediate Language (IL). In fact, it is achieved by language developers to make their language and Visual Studio.NET compatible IL translator. Such languages are called .NET Support Language (.NETENABLED LANGUAGE).
The IL file is usually packaged in a deployable called assembly component (Assembly) unit. These assembly components are loaded into a general-purpose operation language (part of the COMMON LANGUAGE RUNTIME, .NET Framework), compiled by the IL compiler, and then runs within the common running language (CLR). The CLR provides a number of features that we can unite these features with a specific language, including debris collection, type definition, multi-type method resolution, error handling, and deployment model. Combining the language characteristics into a generic running language (CLR) rather than merged into a specific language, making the various languages to be freely interoperable over the entire .NET platform. Debris collection, type definition, and error handling are handled in a unified form, thereby achieving unparalleled language interoperability. Perhaps cross-language interoperability is the most impressive example is a base class in a language (such as C #), and then rewrites various methods in a completely unrelated language (such as COMBOL). The author has given such an example in the recent article. [1]
In the representation layer, use .NET Framework means that any language that supports .NET (in other words, any language with the IL interpretation) can be used as a scripting language representing logic. And since the .NET Framework includes a compiler, it also means compiling the representation layer script, rather than explaining, thereby significantly improvement.
We are seeing that various types of thin clients (browser, cellular phones, electronic writing, etc.) began to grow rapidly, and each client supports their own HTML subset. Today's representation layer script must first determine the type of client and then create a special HTML for the client. This kind of operation is very cost-effective, it is easy to maintain, and it is difficult to maintain when the new client system is available.
Visual Studio.net includes a new representation of a layer program design model, which is designed to simplify the programming of the surgery of the thin client system. This new program design model is called ASP.NET. ASP.NET allows representation of layer logic to be neutralized. This programming model is based on today's very successful VisualBasic program design model. With ASP.NET, the presentation tier scripts ask controls (such as menus or pull down boxes) to act in certain ways, and then respond to events that those controls raise. It then becomes the control's responsibility to deliver its functionality using the HTML best SUITED for a given client device.
Design A ASP.NET application Simply puts the GUI control (such as a menu or drop-down toolbox) from the template to the design desktop. The programmer then writes the code that responds to the control event in any support of the Studio .NET language. By the control, not by the programmer, the best explanation method ASP.NET architecture is responsible for determining a specific action (such as pressing the button) based on the actual device of the client. Since all of this occurs at the representation, the same code base can work correctly, regardless of whether the actual client device is any .NET technology.
Control / Event Program Design Model, which has built-in devices to represent controls instead of logic, thereby greatly reduces the development and maintenance phase. The development work is reduced because a simplified code block can explain the client's needs and process the HTML requirements of any final client device. The maintenance work is reduced because we can join the support for new client devices by downloading the latest version of the control we use. .NET Enterprise Server
The .NET Enterprise Server is a group of additional, designed to provide dedicated enterprise-class server products. Each server product is a separate pricing to provide maximum financial flexibility in configuring overall solutions. A company is only charged for the required service.
The most famous enterprise server is Microsoft's Probably The Highest Profile SQL Server. This is Microsoft's high-end database products that have many functions of this product have far exceeded the scope of this article. It can be said that SQL Server is a relational database with high performance, high availability, high scalability, is a strong competitor in the corporate market.
However, there is no meaning for the user to rely on SQL Server for the .NET platform. Many organizations use the entire .NET platform to create their e-commerce systems, they can choose their own data storage technology, such as Oracle or DB2. Each popular database system can be used as a .NET data layer. For example, Oracle can be accessed through ADO.NET interface in the database. The mainframe database, CICS, and IMS can be accessed via Host Integration Service (HIS).
The latest .NET Enterprise Server is the Application Center Server Server. This product is designed specifically for companies that require 24x7 availability and / or low telescopic costs. Application Center Server is both a cluster coordinator and a cluster manager.
Internet Security and Acceleration Server (Internet Security and Acceleration Server, ISA Server) focuses on the demand of the representation. IT ISA Server provides two important features: HTML page cache, which can significantly improve the performance of many key points, as well as firewall functions. Of course, firewall functions are critical to ensuring any of the security of any important e-commerce site. ISA Server provides a low-cost software solution for hardware-based firewall products. Risks with redundancy, ISA can be used with other .NET products, but this does not need.
BizTalk Server is a comprehensive, integrated product, mainly to link various organizational agencies together and allows the organization to be used to operate with partners.
Commerce Server is an architecture for creating an e-commerce site. It focuses on solving the needs of e-commerce retail business. Use the components provided by Commerce Server and perform specialized to create such a website quickly.
UDDI collaborative infrastructure
Collaboration is the future of electronic enterprises. Industry standard sets that are defined to support electronics can group under Universal Description, Discovery, And Integration (UDDI).
Although UDDI is independent of .NET platform, most UDDI-related activities are advocated by Microsoft. In this way, it seems that the UDDI is more appropriate in the .NET platform section.
UDDI standards are owned by the UDDI.org Association, not strange, the association's website is www.uddi.org. The Association leads by Ariba, IBM and Microsoft, including more than 100 support companies, including Andersen Consulting, Boeing, Compaq, Dell, HP, Ford, LoudCloud, Merrill Lynch, Rational, SAP AG, Sterling and Sun. To learn about the current supporter, please visit the association website. UDDI is established in a set of existing and widely supported basic standards. These basic standards include:
HTTP - standard protocol used to communicate on the Internet. XML - a widely accepted industrial standard for packaging data and organized strings.
SOAP - a rapidly appearing standard (mainly by Microsoft and IBM company), is used to package client work requests and systems as an XML string. SOAP represents Simple Object Access Protocol (this is a confusing abbreviation because it is not simple or not with any object!).
HTTP and SOAP portfolios are considered to be the foundation of all electronic collaboration in the future. In this white paper, when the author discusses SOAP, HTTP will assume that HTTP is used as the transport protocol. Although other protocols (such as those based on information queues) can be used to transmit SOAP requests, this will be impossible in electronic collaboration architectures.
Figure 2 is the most common SOAP protocol based on electronic collaboration architecture. Since it is easier to explain in the example context, the author will use the original electronic enterprise prototype MoneyBroker. Let's take a look at how MoneyBroker uses SOAP and Austinkayaks, and the final result is that Austinkayaks allows customers to pay by MoneyBroker account.
[1] Please refer to the article of Roger sessions in ObjectWatch Communication: Letter from the PDC 2000; The unveiling of microsoft.net (http://www.objectWatch.com/issue_29.htm)
[JM1] IF We're Paying for this White Paper, We Should Make Sure We Have The Correct TaxOmy. Dburner Will Have The Most Current.
