By Topic

Do you know where your architecture is?

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$31 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

1 Author(s)

Confusion over architecture, while not uncommon in software development in general, seems prevalent in middleware. I attribute this to the fact that middleware systems are typically distributed and heterogeneous. In general, distributed systems are difficult to design, implement, debug, and maintain. When you mix in multiples of hardware platforms, operating systems, protocols, applications, and vendors, the complexity can rise to the point where nobody really understands the whole system. When systems span large enterprises and comprise multiple technologies and approaches, their keepers tend to have far more to worry about than the purity of the system's architecture. A company that fails to implement a system architecture is forced to undertake a system rewrite with every move to a new technology. The article discusses how to manage a system so as to avoid these problems.

Published in:

Internet Computing, IEEE  (Volume:7 ,  Issue: 5 )