At my previous employer, we were building out .NET infrastructure,
but still had J2EE infrastructure, as well, so some decisions were
based on interoperability. That being said, most of the future
efforts were going to be .NET based.
My own opinion is that if you're a Microsoft shop, leverage Microsoft
technologies to their fullest potential, meaning WCF in this space.
Obviously, WCF supports WS-* very well, but note that the decision is
on WCF, not on Web Services. I personally haven't looked at how
taking a Web Services first approach would impact how an enterprise
could leverage WCF technologies. Based on what I've read, I think it
may limit it. From what I've read, WCF would be making the decision
of whether generic WS is used or some more efficient Microsoft
mechanism. I could be wrong, however.
There would be nothing preventing someone from building a REST based
system using .NET technologies, however, I also don't think there's
anything Microsoft provides that would make building a REST based
system any easier than using Java and Eclipse.
-tb
On Dec 14, 2006, at 8:23 AM, Gervas Douglas wrote:
I guess there must be quite a few of you who have designed and built a
SOA structure around .NET, even if the resulting system was designed
to also incorporate Java-based systems. Would you have considered
using anything other than WS-* for the .NET-based bit?
Gervas
