loading...
 This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Do You Know Where Your Architecture is?
Septemer/October 2003 (vol. 7 no. 5)
pp. 86-88
ASCII Text
x 
 
Steve Vinoski, "Do You Know Where Your Architecture is?," IEEE Internet Computing, vol. 7, no. 5, pp. 86-88, Septemer/October, 2003.
 
 
BibTex
x
 
@article{ 10.1109/MIC.2003.1232523,
author = {Steve Vinoski},
title = {Do You Know Where Your Architecture is?},
journal ={IEEE Internet Computing},
volume = {7},
number = {5},
issn = {1089-7801},
year = {2003},
pages = {86-88},
doi = {http://doi.ieeecomputersociety.org/10.1109/MIC.2003.1232523},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Internet Computing
TI - Do You Know Where Your Architecture is?
IS - 5
SN - 1089-7801
SP86
EP88
EPD - 86-88
A1 - Steve Vinoski,
PY - 2003
KW - middleware
KW - architecture
KW - abstraction
KW - coding
KW - designing
VL - 7
JA - IEEE Internet Computing
ER -
 
Steve Vinoski, Iona Technologies

Confusion over architecture, while not uncommon in software development in general, seems prevalent in middleware. 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.

Index Terms:
middleware, architecture, abstraction, coding, designing
Citation:
Steve Vinoski, "Do You Know Where Your Architecture is?," IEEE Internet Computing, vol. 7, no. 5, pp. 86-88, Sept. 2003, doi:10.1109/MIC.2003.1232523
Usage of this product signifies your acceptance of the Terms of Use.