| State of Middleware Standards
| ||||
| Middleware Technology | Standard | Standards Body | Status | |
|---|---|---|---|---|
| Data Access |
Remote Data
Access (RDA) ODBC |
ISO
Microsoft |
Part 1-Generic RDA ANSI/ISO/IEC 9579-1:1993
Part 2-SQL Specialization ANSI/ISO/IEC 9579-2:1993 ODBC 3.0 (an API specification only) |
|
| Messaging | None | Message Oriented Middleware Association (MOMA) | N/A | |
| RPC | None | N/A | N/A | |
| Transactions | Transaction Architecture (XA) | OpenGroup | Distributed TP: The XA+ Specification, Version 2 | |
| Distributed Object Technology |
CORBA
DCOM |
Object Management Group (OMG)
OpenGroup |
CORBA 2.0, CORBAservices
Microsoft recently turned over the DCOM specification to the OpenGroup. DCOM is a binary specification; where there is a discrepancy between the spec and the original source code, the source code is the authoritative reference. |
|
| Although it might appear that many middleware standards are at work, this impression is misleading. Middleware is a collection of services, so there is no specific middleware "standard," per se. Instead, standards that apply to the i ndividual segments and interoperability methods within middleware are needed. Consolidation of various middleware pieces may make life easier for developers, but a lack of standards will hind er network managers' efforts to promote the free interchange of middleware services. |
Back to the Article Updated June 6, 1997 |












