Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

serious advantages of java web service over .net web services- please help

 
vamsee krishna reddy
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi freinds

i have to give a presentation on the advantages of java web(i am planning axis) services over . net web services.

and this is also going to decide on which technology my new project need to be developed.

any kind of difference which makes a statement is most welcome.

help me get the project
 
Balaji Loganathan
author and deputy
Bartender
Posts: 3150
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
That shouldn't be the approach to start with.
You should base your software stack based on your client's existing technology stack.
Otherwise, the client get into the trouble of maintaining two difference stacks.

IMHO, both .NET and Java were well matured now and so it wont be wise compare it at basic level.
So it is better if you can try to address what exactly Java web services can provide solution for a specific problem that .NET can't.
Regards
Balaji
 
Jimmy Clark
Ranch Hand
Posts: 2187
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
A description of the proposed applications that will use the web services would be helpful.
 
vamsee krishna reddy
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
James Clark wrote:A description of the proposed applications that will use the web services would be helpful.


the client applications are developed in both .net and java(struts), database is in linux , even this web service will be deployed in linux i guess.
and all the services are accessed on intranet, only the client applications will be exposed to the internet
 
vamsee krishna reddy
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Balaji Loganathan wrote:Hi,
That shouldn't be the approach to start with.
You should base your software stack based on your client's existing technology stack.
Otherwise, the client get into the trouble of maintaining two difference stacks.

IMHO, both .NET and Java were well matured now and so it wont be wise compare it at basic level.
So it is better if you can try to address what exactly Java web services can provide solution for a specific problem that .NET can't.
Regards
Balaji


thanks for your reply balaji

as you said both IIS and tomcat will get the job done perfectly. but to grab the work we need to show that we have some edge over others, so i was expecting some differences like tomcat is very lite weight server compared to IIS.!!!............
 
Ulf Dittmer
Rancher
Pie
Posts: 42967
73
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
+1 on what James said. You're doing it backwards - start with the requirements.

WS are a language- and OS-agnostic technology. It doesn't matter which language the client is implemented in, nor does that have any impact on the server. It's possible to implement highly functional and well-performing WS using both Java and .Net, using any number of servers and SOAP toolkits. Starting with those is unlikely to help with making a sound decision about this.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic