Perspective and Adjust your business and business system (V: Solution, Architectures)
Small gas god 2001-10-15
Ok, I want to end the entire topic after this, it seems that some conclusions may be different, and the specific situation in each person may be different, the environment is different, so it can only be thought about it. Some features in DOTNET make people feel very excited, but we can't always use new technologies to re-start architecture our needs and applications, whether it is migration or transformation, we need our serious examinations and inspect, build procedures and code, often start One decision is an important one. However, this is often a (Haha) that is still in the quagmire.
First explain the entire environment and the software you need:
1. Windows 2000 Advanced Server SP2 (English)
2. Windows 2000 Advanced Server SP2 (Chinese Simplified)
3. Microsoft SOAP Toolkit 2.0 SP2
4. Microsoft Visual Studio 6.0
5. Microsoft SQL 2000 (Chinese Simplified Enterprise Version)
6. Microsoft Visual Studio.NET Beta 2 (English)
7. Microsoft Visual Studio.NET Beta 2 (Chinese Simplified)
8. Microsoft IE 2600 (English)
I have explained in front of the three machines, HenrySVR is the W2K and VS.NET in English, and the DEREKSVR is Chinese Simplified W2K and VS.NET.
The final architecture has also been adjusted to this (as shown below), in which it seems to have the smallest impact on the current system, the original application architecture does not have to change, and the new demand can have a new starting point. And how to implement this layer of WebService, you can decide on the above discussion. MARY Kirtland (very familiar) has an article "A Platform for Web Services" is very good, especially the endmap_1.gif ended, should not let go, Treasure map.
Http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwebsrv/html/websvcs_platform.asp
http://msdn.microsoft.com/library/en-us/dnwebsrv/html/roadmap_1.gif
As for the final DOTNET architecture, I think it is still changing, but some are certain, such as DOTNET more distributed more distributed and more loose than previous DNA structures; more loosely updated DB and BIZ layers. Freedom, it won't be so hard. The architecture of the expropriation is the case, put forward a new time, in-depth understanding of the time, starting the application takes time, real application is widely accepted for a while.
Description and conclusions:
1. The above discussion is based on such a premise: you have a system or application system (preferably Window DNA structure), you want to transform and make adjustments to make it up with DOTNET technology. If everything is new, then the part of the above-mentioned interoperability is helpful, after all, the Window DNA structure and new DOTNet program architecture are different. Please consider the new architecture, two The data layer of the system and the division of business logic layers have been greatly different. 2. I didn't consider or tell the firewall to consider and test, in practical applications, Ignore the firewall may be fatal. That is to say, special firewall deployments may result in the structure described above. For example, a single firewall, the port of HTTP and DCOM in the firewall.
3. Since DOTNET and VS.NET are currently beta, the security, performance, and release time are confidential and subject to protected, then it will not be able to compare or test the existing COM / DCOM or Java for performance, etc..
4. The entire discussion does not involve another technology of DOTNET: Remoting, which will also be a factor and technology hotspot, but the above discussion covers the combination of Remoting services to all possible clients and server-side, effect is Similar, there are many different implementations. Remoting technology can control more deeper and specific, more interactive for remote objects or components.
5. More obvious feelings are DOTNET systems, communication and cross-platform access between different platforms seem to have resolved. XML importance is enhanced. Then the problem that may bring later is: If you are a developer, how you will choose your own platform. What platform will you program on?
6. The interoperability of the DOTNET and the current COM, COM , DCOM, etc. under the Windows platform are very good. In compatibility, MS gives up some, but interoperability considers a lot of interoperability, the same problem can be completed. The key is that you take that way. This reminds me of Anders Hejlsberg for the description of "Interoperability" (http://www.9cbs.net/develop/read_article.asp?id=9615). With this MS or you can win a lot of programmers.
7. For the choice of the model, I only use the most basic logic to simulate, and the actual situation is much more complicated. Besides, there is no consideration, the COM and component deployment in the entire Windows environment is actually the trouble and needs enough courage. In addition, some of some of the logic of components should be complex (such as more components) or the actual environment is complex (such as multi-distribution to several machines), this may be better.
8. Whole process We examine Server is a DOTNET. The client can be VB or current technology; the server side is COM / DCOM. The client is a variety of combinations such as DOTNET, which is afraid to be too far, so the client and service are Is the situation in DOTNET. However, the focus seems to be finally returned to WebService.
Thank you for speaking this article, I hope to face the new and old system, do some important decisions: maintain the original or rewrite; how to build how to start this back, you must do decisions, you must inspire and help . Finally, let me use Anders Hejlsberg as the end:
"We've tried not to take an" ivory tower "approach to engineering C # and the .Net framework. We can not afford to rewrite all of our software. The industry just can not afford it, especially now when we're moving on Internet time. you've got to leverage what you have, and so I think interoperability is just key. We focused hard on giving programmers all of the right solutions for interoperating with Internet standards, such as HTTP, HTML, XML, and with existing Microsoft technologies, so you do not fall off a cliff the minute you find that something is not provided by the new .NET environment, or when you realize you want to leverage some existing API or component. you've seen all THE COM Interoperability That We Have Built Into The Language and Into The Common Runtime; "--- Anders Hejlsberg
especially:
The above text and pictures involve other people's privacy and personal rights, such as non-authorized or agree, please do not publish, reprint, adapt, repost, or other forms of communication. All of the above texts and images are only used for internal communication, and do not make any news publishers and commercial purposes.
