Language
In terms of language, choose very simple. J2EE supports Java and only supports Java. In the foreseeable future, it will not support any other language. The .NET platform supports any other language other than Java (although it supports a language, C #) that is quite equivalent to Java, C #). In fact, if the .NET platform is as important as a language independent vehicle, it is likely to support the .NET platform in the near future.
Some companies drive J2EE to support other languages. Although IBM's WebSphere and BEA's WebLogic support other languages, they are not implemented through J2EE technology. In J2EE platform, there are only two formal ways to access other languages, one is through Java Native Interface, and another method is to intermo it through CORBA. Sun is recommended to adopt a latter method. Just as Sun's famous scientist and Java designer Rick Cattell said in an interview:
You can call C through the Java Native Interface feature and C via CORBA. CORBA may be a recommended approach because it passes more flexibility and we have designed J2EE [1] that can work together with CORBA in an approved environment.
Creating any new code in the CORBA architecture is a very problematic policy. CORBA is a favorite architecture in the 1990s, but it is no longer used. According to the author, there is no CORBA developer (except Iona) earnings on CORBA, and there is no developer (including Iona) to continue to invest in this technology. The bottom line is if someone wants to develop any language other than Java, then J2EE is an incorrect platform selection.
Some non-Java currently is considering the possibility of re-standardization on Java. To achieve this, there are three possible methods:
Rebond new staff for existing staff, and replace existing staff outsourcing as much as possible
Rehabilitation may be the most expensive choice. With my experience, there is a lot of management costs related to the traditional programmer training into an object-oriented Java programmer. This is the result of the recent research of the Gartner Group, and it is concluded that a Cobol programmer training into a Java programmer, and each person takes approximately $ 60,000 [2]. The author believes that for Visual Basic programmers, the cost is substantially. And at the end of training, you have no time in productivity. You can simply hire a code that can now be written and the code written after 20,000 US dollars, but now you can use Java to write programmers. In many companies, the author once sees that due to the case of object-oriented technologies, working hours are often wasting the theoretical discussion of endless and no results on the "correct" object-oriented design and analysis.
Employment and / or replacement staff is expensive. Currently, the salary requested by the Java programmer is 30% higher than the traditional Visual Basic / Cobol programmer. In the experience of the author, they have a higher new employment ratio.
For companies that want to turn to Java, outsourcing may be the only feasible choice. However, assuming outsourcing can completely enhance the problem mentioned above, it is clear, especially the additional programmer cost is transferred to you, even more.
So what language do you use? The bottom line is that if you have a Java training staff, and there is already a suitable strategy to ensure the effective management of the program design process, then do everything else. The author likes to use Java as a programming language, although the author thinks there is at least other good languages. On the other hand, if your store is mainly composed of Visual Basic and Cobol, then the steering Java will definitely be expensive, frustrating an experience. Your language choice will not determine your choice between J2EE and .NET platforms. Of course, if you want to use some things outside Java, then you are in J2EE space. However, Java's appeal does not need to deprive your right to use the .NET platform. The .NET platform includes support for C # (pronunciation to C Sharp), which is a language similar to Java, so that many people cannot distinguish them. A experienced Java programmer can learn C # syntax within a few hours.
However, if you choose Java not because J2EE claims a portability strategy, C # or any other language that can be run on the .NET platform is unlikely to make you happy. If this is, it is clear that J2EE is your choice. However, before making a selection, you must read the chapter on the portability. .
portability
Many of J2EE's appeal is the commitment of portability. There are two portability. One of the developer portability. The author called this portability as a developer neutrality (Vendor NeutRality), which has been discussed (and refused) this idea. The second portability is the Operating System Portability. This refers to the ability to transfer the code base from one operating system from one operating system to another without any changes to the code. Unlike developers, most J2EE implementation is most likely to take the operating system portability.
J2EE is most likely that the operating system is portable, is largely not due to any inherent portability of J2EE, but most J2EE developers support a variety of operating systems. Therefore, it is possible that as long as a company is loyal to a established J2EE developer and a established database developer, it is possible to turn to another operating system from an operating system. This may be the only one of the most important J2EE platforms exceeding the .NET platform, and the .NET platform is limited to Windows operating systems. However, Microsoft submits a subset of C # specification and .NET Framework to ECMA (a group that standardizes JavaScript) (called Common Language Infrastructure) without value.
Why is the developer portable / neutrality and satisfactory, but what is the benefit of portability of operating system? We recognize that there are two types of companies that require operating system portability: Independent Software Developers (ISV, INDEpendent Software Vendor and companies seeking contractability).
Independent Software Developers (ISV) requires operating system portability when there is a large number of non-Windows platform customers. A developer is impossible to sell one product to UNIX customers depend on the .NET platform. If the .NET platform is better than J2EE, it is not good. It is not running on UNIX.
If the independent software developer's product must be sold to non-Windows customers, especially when the J2EE platform itself needs to be bundled with independent software developers, J2EE provides an acceptable solution.
If the independent software developer's main customer base is Windows customers, then the .NET platform should be selected. It provides much products with much lower cost.
Many companies that need to operate system-portability are not independent software developers. Most companies' companies believe that portability is a path to contractability. These companies believe they, with the expansion of throughput requirements, they can get higher contraction by transplanting the application to a higher-end hardware platform. If you believe that the operating system can contract to help you get shroomable in any way, you are making a serious mistake. Contracted is not a hardware problem; it is a software problem. The highest contraction can be obtained by seeking a highly contracted platform and then serves as much as possible. The J2EE that is running on multiple platforms is implemented, and it takes a long time in terms of receivability. So far, in terms of high-contractability, the best proven platform is .NET platform.
Use the author to give the number about the contractability of the contractability, the .NET platform can increase from 16,000 transactions per minute to more than 500,000 transactions per minute. IBM WebSphere J2EE / UNIX technology is one of the best representatives of J2EE, which may not be better than handling 17,000 to 110,000 transactions per minute, while the cost of each transaction is higher.
Therefore, portability is not as simple as it looks. If you really need a contractability, it is obvious, in the .NET platform and J2EE, .NET platform is a winner. If you have to support non-Windows platforms, it is obvious that J2EE is a winner.
If you need portability, don't rely on a moment of thought or a specific independent software developer, so forget it. This portability does not exist at all. So you have to take care of the developer seriously. Confident, you understand and feel satisfied with the developer's technical guidance. Great to your developer has a long-term commitment to the platform. Finally, it is sure that your developer has financial resources to survive on this highly competitive stage.
Client equipment independence
The author discussed the difference between the Java and .NET platform representing the layer program design model. Main differences, using Java, decided to transfer the ultimate HTML to the client to the client, and use .NET, the Visual Studio .NET control.
This Java method has three problems. The first question, it requires a lot of code that represents the layer, because each possible thin client does a different code path. The second question is difficult to test the code using each possible thin client system. The third issue is difficult to add new thin clients to existing applications, as this will involve search and modify the number of amazing representation layer logic.
The .NET Framework method is an independent code that is written with an inter-visual control interactive. Responsible for determining what HTML for transmission based on the client device is control, not a programmer. In the .NET Framework model, a person may forget something like HTML!
This method solves all three problems of the Java / old ASP method. A person can use less code. Testing the code is easier, as you only test the interaction with the control, not the client device. Finally, you can easily add new client devices, just download the latest version of the latest knowledge about thin client devices.
From a cost perspective, .NET Framework method is no doubtful winner. If the layer developer is no longer responsible for determining which content displayed on the client device, it will easily be much easier (, much more cheap).
in conclusion
For e-commerce architecture, we have two mutual competitors.
Sun's J2EE concept is based on a family specification that many developers can implement. Any company can permit and implement the technology. In this sense, J2EE is open, but from only one developer controls the technology, it is closed, it is a very limited and external interaction Self-satisfied architecture of island.
One of J2EE's main disadvantages is that choosing this platform indicates using a programming language, a language that is not suitable for most companies. One of J2EE's main advantage is that most J2EE developers provide operating system portability.
Microsoft's .NET platform idea is a product, rather than a norms that use to define interoperability points. The residence of this method is that if it is limited to the Windows platform, the application written for .NET platform can only be run on the .NET platform. There are several important advantages: Net platform:
Developing applications is lower, because you can use standard business languages, and you can write independent representation layer logic.
The cost of running the app is lower because the item hardware platform can be used (cost is 1/5 of their UNIX opponents).
The ability to telescopic is larger, proved to support the client number is 10 times the number of clients that can support any J2EET platform indicated. The interoperability is stronger, and the industrial standard electronics can be built into the platform.
The most different feature of these two platforms is the portability of the entire system. Companies seeking cost e-commerce platforms may ignore the functions provided by Microsoft due to negligence. E-commerce always requires high reliability and excellent rehabilitation. For the first time, these functions can be obtained on the commodity hardware platform with a small part of UNIX-based solutions.
