Has reading this article changed your opinion about using shared databases and enterprise messaging for your interoperability solutions? Although this solution is the most mature, it's not usually touted in interoperability articles. Why, do you think? Is it because vendors have already sold these solutions and tech authors have already exhausted the topic, or is it because people prefer to use the latest technology rather than possibly the best solution? Let us know in the .NET Technical or discussion forums.
Java/.NET Interoperability via Shared Databases and Enterprise Messaging
Using technologies such as shared databases and messaging to provide Java/.NET interoperability may not be as sexy as Web services or binary interoperability, but offers the least risk and the greatest flexibility.
by Kyle Gabhart
January 21, 2004
un's Java 2 Enterprise Edition and Microsoft's .NET Framework represent the two undisputed titans of n-tier, enterprise software platforms. Although most IT departments will standardize on one of these platforms as their exclusive dance partner, it's often necessary and sometimes even desirable to tango with both platforms.
Other articles in this special report cover Web services and binary Java/.NET interoperability, but those aren't always the best solution, particularly when your applications depend on asynchronous processes. In this article you'll see two additional interoperability solutions: a shared database and message-oriented middleware. Although these two approaches are considerably less trendy than XML Web services, and perhaps not as exciting as binary interoperability solutions, they are more established, and in some cases more viable, integration solutions.
It's quick, easy and you get access to all the articles on DevX.
This registration/login is to allow you to read articles on devx.com. Already a member?
To become a member of DevX.com create your Member Profile by completing the form below. Membership is free!