|
Friday, August 30, 2002 |
|
So I am trying to participate in an objective comparison of IBM's WebSphere and Microsoft's .NET/COM+ technologies. In a large enterprise there is clearly room for, and a need for, both. However, is one really better than the other for creating high-volume web-based transaction processing applications? If committment to a particular vendor and portability are not major concerns, is there really a major difference between the two visions? I suspect not. You have to give IBM the nod for better integration with their own platforms (notably CICS and the AS/400). OTOH, Microsoft is emerging as a clear winner in the scalability/performance numbers according to the Transaction Processor Council. ASP.NET also provides a very impressive platform for developing the presentation layer. WebSphere may be less risky, being a somewhat older platform now in its fourth release. OTOH, COM+ has gone through some major evolutionary changes (from MTS). Ditto for .NET. That is to say, .NET and COM+ may be relatively new from a release standpoing, but they have some heritage behind them in terms of learnings from past/other technologies (COM/DCOM/MTS/Java/ASP/JSP). Oy vey, how to make a rational decision? 10:15:02 AM  Google It!
|
|
Component Oriented Middleware (COMWare) is a term coined by Roger Sessions to describe the software landscape where transactions and components mix it up. COM+ and J2EE implementations are the two most widely recognized COMWare platforms today. What makes up COMWare? I pulled these definitions from Roger's book COM+ and the Battle for the Middle Tier
9:59:36 AM Google It!
|
