Download ppt - Sreerag dot net vs j2ee

.NET Vs. J2EE

MICROSOFT’S .NET TECHNOLOGY – OBJECTIVES & ARCHITECTURE

Sreerag Gopinath P.C,

Roll No. 24,

Semester VII,

Computer Science & Engg.,

SJCET, Palai

The great debate: .NET Vs. J2EE

1. Specification set Products & Services

2. Server-focused Complete platform

3. Hard to develop for Easy, supports RAD

4. Multi-platform Currently only Windows

5. Single language - Java Multi-lingual

6. Multiple vendors Single vendor

7. Behind .NET in price /

performance ration

Better price/

performance ration

Why should you choose .NET over J2EE?

.NET offers multiple languages. Addresses the open source standards – XML,

HTTP, SOAP. J2EE does not implement SOAP.

Built-in XML support for messaging,& interface exporting. EJB does not.

Much more promise for interoperability.

An Experienced Professional Shares his Experience…

No Reservations About .NET – Larry O’Brien

Read the complete article at –

http://www.sdtimes.com/article/column-20031015-04.html


“ I’ve had the relatively rare luck to work on extremely similar projects (GDS) in .NET, Java 2 Standard Edition and Java 2 Enterprise Edition. My wholehearted favoring of .NET over the J2EE platform, while supported by theory and analysis, is driven by my experiences developing and shipping these applications.

Aside from the business logic, the .NET project took 80% of the J2SE project’s time with less than 75% of the manpower.

But what really proved .NET’s value proposition to me was when I saw how the subsystem was integrated. When you witness the ease with which minimally experienced server-page

programmers can successfully participate in developing a distributed application by consuming Web Services developed by more experienced programmers, you become a believer.

When you witness developing programmers transitioning into a more object-oriented approach because using Visual Basic .NET they can do so seamlessly, and then you go back to your workstation and see the curly brackets of C#, you realize that what’s really being integrated is not subsystems, but the programming team. What’s being turned into a coherent whole is not code, but coders. And that’s why I choose the .NET platform. Without reservations.”


Benchmark Tests

http://www.gotdotnet.com/team/compare/benchmark_response.pdf

Web Services Performance

In June 2004, Sun Microsystems published a benchmark showing the relative performance of Microsoft .NET vs. Sun™’s Java Web Service Developer Pack on a series of simple Web Service tests. The paper describes the results of testing these re-created implementations. Microsoft has also created several additional tests of Web Services on each platform to illustrate the relative performance when the backend Web Services are required to do more work. These additional tests are more realistic than Sun™’s tests, and show the relative performance when the Web Service message payload is increased. .NET results are actually more than two to three times better than Sun reported. In Microsoft tests, .NET roughly matched or slightly exceeded J2EE performance for Sun™’s four original tests. Furthermore, in the additional more realistic tests involving higher Web Service message payloads we found .NET to significantly outperform Java.




Nile Application Benchmark results

See how Microsoft .NET compares to the scalability and performance of a leading J2EE-based application server. In this study of an end-to-end e-commerce benchmark application, we detail performance results for several implementations of the Nile benchmark on a variety of hardware configurations. The implementations tested include Nile ASP.NET/C#, Nile ASP/VB COM+, Nile ISAPI/ATL Server/C++, Nile JSP, and Nile EJB. See how .NET stacks up against these other technologies in this comprehensive benchmark.

Nile Application Benchmark results

References

http://www.gotdotnet.com/ http://www.java.oreilly.com http://www.microsoft.com/net http://www.javaworld.com/ http://www.sdtimes.com/ http://www.learningcircuits.org/ http://www.astd.org/ http://www.sun.com/ Professional .NET Framework, Kevin Hoffman, Jeff

Gabriel et al., “Apress”.

.NET Vs. J2EE

MICROSOFT’S .NET TECHNOLOGY – OBJECTIVES & ARCHITECTURE

- Sreerag Gopinath P.C