Data is the most important part of an application. Almost every application needs to operate on data— whether it’s creating, consuming, or processing data. Without data, almost all applications would be useless. You can use many patterns when designing applications to work with data. In the early days of client-server applications, a favorite approach was the n-tier approach, where the application was divided into n tiers (the most common division was three tiers). In the three-tier approach, the first tier is the presentation tier, which handles all the presentation of the application (the UI), and is essentially what the user interacts with. The next tier is the business layer, which contains all the business rules to which the application needs to adhere. The last tier is the data layer, which performs the create, read, update, and delete (CRUD) functionality. The data layer usually connects to the required back-end data sources using one of many well-known mechanisms, such as OLE DB or ODBC.
KeywordsOrder Property Incoming Message Message Class Soap Message Inheritance Hierarchy
Unable to display preview. Download preview PDF.