Remember the days of Mainframe’s? The large, sophisticated and costliest systems of their times have been replaced by the new Java, C++ and VB programs. Not only this, new languages with web 2.0 orientation like Ruby on Rails are now making their mark in the market leaving us with hardly any reminisces of the legacy systems.
But then, arises the question, is anybody still using the mainframes? Answer: Yes, they are using them. Why? That’s because it’s just too costly and disruptive to go through the entire system implementation procedure just for a new technology. Moreover, these systems work.
So what’s the issue? The issue is that organizations keep buying new systems to optimize its business processes, and these new systems need to communicate with the legacy ones. But none of the systems were ever designed to communicate with others. So we need to somehow integrate them.
And this issue is not just limited to information exchange between the legacy and the new systems, the problem exists with any communication between different systems. Following are some of the technologies which are presently being used for integration, and who else but the usual suspects (Microsoft, Sun etc.) have been behind them:
CORBA – Integration across multiple languages and multiple platforms
JRMI – Integration across multiple platforms talking in JAVA
DCOM – Integration across multiple languages in Windows
JMS – Java Messaging Services
Web Services – SOAP and XML
