Skip to content

.NET Versus J2EE

August 7, 2009
tags:
Microsoft.NET versus J2EE.
Features
J2EE
Microsoft.NET
Type of technology.
Standard
Product
Middleware Vendors.
30+
Microsoft
Interpreter.
JRE
CLR
Dynamic Web Pages.
JSP
ASP.NET
Rich Client API
Swing
WinForms
Middle-Tier Components.
EJB
.NET Managed Objects and COM+
Operating Systems
Win32, Solaris, Linux, OS X, many others Operating System.
Win32
Distributed Transactions
JTS
.NET Distributed Transactions
Message Queuing
JMS
MSMQ
Program Packaging
Jar Files (.jar)
Assemblies (.exe and .dll)
DataBase access.
JDBC, SQL/J
ADO.NET
Web Services
JAX Pack API
Built-in .NET SOAP classes and Microsoft SOAP Toolkit
SOAP, WSDL, UDDI
Yes
Yes
.NET:
  • If there is need to develop the application within a short period of time.
  • If the end user is ready or willing to bear the cost of .NET, Microsoft operating system and server licensing.
  • If human hours cost more then licensing cost.
  • If there is no need to reuse and scale functionality of application.
J2EE:
  • If the system is having very complicated requirement and has very large scope of functionality.
  • If there are requirement to reuse and scale system functionalities.
  • If there are fewer constraints over time taken for development of application.
  • If the end user if not willing to bear cost of licensing .NET and other related products.
  • If there is requirement to deploy and run the application other then Windows platform.
Advertisements
No comments yet

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: