ADO.NET brings with it a number of benefits, which fall into the following categories:
The ability to communicate across heterogeneous environments.
The ability to serve a growing number of clients without degrading system performance.
The ability to quickly develop robust data access applications using ADO.NET’s rich and extensible component object model.
An improvement over previous ADO versions due to the disconnected data model.
All communication involves data exchange, whether the communication between distributed components is through a request/response methodology or a message-based facility. Current distributed systems assume that the components involved in the communication are using the same protocol and data format. This assumption is too restrictive if the client base must expand to cover the enterprise and beyond. Data-access layers should impose no such restrictions.
In current Microsoft Windows Distributed interNet Applications (DNA) Architechure, application components pass data back and forth as ADO disconnected recordsets. This requires the data-providing components, as well as the data-consuming components, to use the Component Object Model (COM). The payload, the actual content we are passing around, is packaged in a data format called Network Data Representation (NDR). These NDR packages are streamed between components.
There are two issues with current Windows DNA systems. ...