Choosing a middleware for web-integration of a legacy application

Authors:
Sakib Abdul Mondal;Kingshuk Das Gupta
Affiliations:
Infosys Technologies Limited, Infosys Towers, Bangalore 560 076, India;Infosys Technologies Limited, Infosys Towers, Bangalore 560 076, India
Venue:
ACM SIGSOFT Software Engineering Notes
Year:
2000

Citing 3
Cited 1

Messaging and queueing using the MQI

Messaging and queueing using the MQI
Middleware: a model for distributed system services

Communications of the ACM
Mastering the Middleware Muddle

IEEE Software

Systematic Approaches for Designing B2B Applications

International Journal of Electronic Commerce

Quantified Score

Hi-index	0.00

Visualization

Abstract

Business applications today often face two contradictory constraints: they have to deal with heterogeneous platforms and at the same time meet the quality requirements. A larger number of middleware products are available to meet the first objective. An architect invariably faces a problem of picking up the right kind of middleware for the problem at hand. Fortunately, the second objective of quality requirements help an architect narrow down the choices of middleware. In this article, we demonstrate this fact through a project of web-integration of a legacy invoicing system.