BabelTubes are TUBE® powered dual-node pipes revolutionising the interaction between disparate middleware protocols or message formats.
Their simplicity and ease-of-use dramatically reduces the timeframe and risks inherent in any point-to-point integration activity, while providing a robust end point abstraction mechanism that can be leveraged in future-proofing any contemporary distributed architecture.
All BabelTubes also feature integration test automation; support, allowing projects to break the dependency between endpoint availability and end-to-end architecture validation by providing the test team with ready-made stubs specifically for this purpose.
This simple-sounding feature has been shown to systematically reduce testing difficulty and timeframes across various integration projects. Moreover, when an end point becomes available BabelTubes render the transition to full end-to-end testing seamless.
All this in a fast performing, robust software component with a tiny application footprint and no centralized server requirement, BabelTubes have been providing glitch-free interoperability in the systems of satisfied customers for many years.
Olinqua offer three distinct types of BabelTube:
| Industry | BabelTubes that have been pre-assembled to support a bridge between two industry standard interface types. |
| Individual | BabelTubes that are assembled on-demand to meet each and every unique customer interoperability requirement. |
| Specialty | A special set of pre-assembled BabelTubes that offer special functionality over and above a point-to-point bridge between two interfaces. (e.g. XML compression) |
Note: Only Java-native BabelTubes are currently available.
.NET native BabelTubes are scheduled for release in Q1 2011.
Q. When would I use BabelTubes?
A. When integration requirements, for example into legacy systems, are unlikely to be efficiently fulfilled by the middleware underpinning your project; or when interfaces are expected to change and hand-coding the required wrappers would take too long and cost too much to maintain; or you simply wish to derive a longer term benefit by standardising and improving your organisation's approach to system interoperability - but want to do this in stages.