Choosing a middleware for web-integration of a legacy application

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.