After completing several small projects with WCF, I can do that very happy with it.
However, have spent a little time looking for alternatives, what I am struggling to gain from the use of Java-based web services such as XA2 or Metro
< P> Clearly, the source is probably one of them and it is also getting away from Windows Server / IIS, but I can not see anything much?
In particular, compared to these two approaches, I will evaluate between two between your two productivity . Suppose that you have either an option to chase / or, I have been found to work more closely with Metro and Axis 2 than WCF.
Given that these two are essentially access points, the complexity of the system is the important decision point behind the scenes in terms of compatibility. Although we live in the world of unlimited interop possibilities, I like the pile where continuity can achieve productivity and performance benefits.
For open-source, while there is more volume than Java. NET, I have also found that those extra projects are supported, which are Java Web Service Platform (for example, For) Supports unavailable functionality.
Getting out of Windows / IIS is definitely an option with Java / Metro / Axis 2, while with WCF you are stuck in your front-end server. I have personally found both (also) configurations to be overwhelming, so neither has worked as a benefit for me in this regard, although alternative hosts of Java combinations are definitely a possibility, in some situations The higher the value is.
Everything else, there will be scenarios in both platforms (in total) where they are more advantageous besides this. Where those conditions apply in your environment, I find the most relevant.
Comments
Post a Comment