Challenges faced by developers
The data services tier is responsible for the:
In Windows DNA applications commonly implement their business logic using one or
more of three implementation options.
Writing much business logic in ASP pages is a bad idea. Since simple languages are
used, such as Microsoft Visual Basic Script, and the code is interpreted each time it is
executed, which hurts the performance. Code in ASP pages is also hard to maintain,
largely because business logic is commonly intermixed with presentation code that
creates the user interface.
logic as COM objects. This approach is a bit more complex than writing a pure ASP
application. Wrapping business logic in COM objects also cleanly separates this code
from the presentation code contained in ASP pages, making the application easier to
maintain.
The Third option for writing business logic is to create some of that code as stored
procedures running in the database management system (DBMS). Although a primary
reason for using stored procedures is to isolate the details of database schema from
business logic to simplify code management and security, having code in such a close
proximity to data can also help optimize performance.
In Windows DNA, there are two major choices of user interfaces - Win32 clients and
browser based clients. During the Internet revolution of the late 90s we saw the
emergence of the browser and the Web Server. With the introduction of Internet,