| Research | Community | Analysts | Teleconferences | Events | Consumer Data | Business Data | Executive Programs | Consulting | About Forrester |
| Primary Analyst Photo | Document Information | Rate this Document |
|---|---|---|
![]() |
January 31, 2006 Choosing The Best Option For .NET-Java/J2EE Interoperabilitywith Randy Heffner, Mike Gilpin, Andrew Sahalie |
|
This is an excerpt
Now that Java/J2EE and Microsoft.NET are the primary programming models for enterprise applications, developers must often interconnect the two to create applications. In marketing presentations, IBM, Microsoft, and other platform vendors often advise use of Web services to attack .NET and Java/J2EE interoperability. In reality, even these vendors agree that Web services are ideal for loosely coupled integration but inadequate for other requirements. Integration and porting technologies for these purposes are available from both the platform vendors and specialists like Codemesh and Mainsoft. Eventually, Web services technologies will be more broadly useful, but in the meantime, alternatives to Web services will be essential for many clients.
This is an excerpt
Price: US $1749
Our Money-Back Guarantee: If you are not completely satisfied, return it for a full refund within three weeks of your online purchase.
Already a Forrester Client?
Log in to read this document.
Application Development, Architecture & Technology Strategy, Application Infrastructure Technologies
Footer links (2 lists of links) |