Q

What is the data access implication of Service-Oriented Architectures?

What is the implication on data access (JDBC and ODBC) of Service Oriented Architectures? Please contrast with data access via these protocols in the Client Server Architecture.
The key to remember when accessing data in a SOA is to ensure that the business logic and data access code are separated. This keeps the business logic as simple as possible, and focused on solving the problems of the business. This separation also provides flexibility, allowing the business logic to remain unchanged even if changes occur in the way the data is accessed.

The Data Access Object (DAO) pattern is a common approach to keeping the data access code separated from the business logic. The DAO may be implemented using JDBC / ODBC or other means.

The separation of the business logic from the data access logic is a logical division. This separation typically is not a physical separation, allowing both to reside on the same tier. The physical division is between the DAO and the data itself. Therefore, this pattern is also effective when building client/server applications.
This was first published in December 2002

Dig deeper on Service-oriented architecture (SOA) development

Pro+

Features

Enjoy the benefits of Pro+ membership, learn more and join.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

0 comments

Oldest 

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

-ADS BY GOOGLE

SearchSoftwareQuality

SearchCloudApplications

SearchAWS

TheServerSide

SearchWinDevelopment

Close