Choosing a middleware for web-integration of a legacy application
ACM SIGSOFT Software Engineering Notes
EDO '00 Revised Papers from the Second International Workshop on Engineering Distributed Objects
J2EE support for wireless services
Journal of Systems and Software - Special issue: Software engineering education and training
Hi-index | 0.00 |
For many software-development managers, staying abreast of the many new technologies that affect the systems we build is nearly impossible. One of the most complex and confusing technology areas is middleware-the cornerstone required to build enterprise-scale distributed systems. Within this esoteric technology domain, it's all too easy to hold up our hands and declare that the outlook is bleak for any kind of consensus on the direction distributed systems will take. Enterprise application integration issues, the nuances of competing middleware products from lots of vendors, and several overlapping standards activities all contribute to the confusion and uncertainty. To help us make sense of the middleware muddle, I discuss the key concepts and issues involved. To better understand recent progress in this arena, the focus is on current best practices for building enterprise-scale systems. That way, we can assess the current state of the technology and its impact on potential future strategies for distributed-systems developers. I begin by generalizing that any successful solution in enterprise-scale software engineering has four key elements: processes, infrastructure, tools, and adoption services. I briefly review current best practice in each of these four areas