|
Anecdotally, in hard core investment banking at least, Java platforms are more popular for real services because they generally perform better, scale well and are more robust. This doesn't mean that J2EE is flavour of the month. Often they cut down J2EE or useĀ something like Spring and Mule rather than a heavy J2EE stack. .NET is seen as a better integrated but not often seen as the core technology for service delivery. Rather it is seen as the gateway to the desktop or as the front office core development technology that fits with Excel. This is why interop between Java and .NET is so important because you always need to connect front office to back office functions in a reasonable way. Web Services is a pretty reasonable way of achieving this and one often finds a mixed bag in terms of what an SOA is. It is often a mix of classic Web Services coupled with more JMS/MOM based service architectures. Just my humble observations. Cheers Steve T On 2 Aug 2006, at 17:37, Ted Slusser wrote:
SPONSORED LINKS
YAHOO! GROUPS LINKS
__,_._,___ |
- Re: [service-orientated-architecture] Re: Platfor... Steve Ross-Talbot
- [service-orientated-architecture] Re: Platfo... Gervas Douglas
- Re: [service-orientated-architecture] Re: Pl... Patrick May
- Re: [service-orientated-architecture] Re... Keith Harrison-Broninski
- Re: [service-orientated-architecture... Dan Creswell
- Re: [service-orientated-architecture... Stefan Tilkov
- Re: [service-orientated-architec... Keith Harrison-Broninski
- Re: [service-orientated-arc... Andrew S. Townley
- RE: [service-orientated... Apps, John
- Re: [service-orientated... Keith Harrison-Broninski
- [service-orientated... Gervas Douglas
