| |
| The Windows Distributed interNet Applications Architecture (DNA) is a framework for building scalable, enterprise applications that combine the attributes of both the Internet and personal computers. |
| IrisLogic teams are fully-qualified and experienced in developing applications that adhere to this framework and our Irisians have built and continue to provide applications to our customers using this robust, scalable architecture to meet their business requirements. Windows DNA applications use a standard set of Windows-based services that address all tiers of distributed applications, including user interface and navigation, business processes, and data storage. |
| At the core of DNA is the integration of web and client/server application development models through a common object model. Windows DNA uses a common set of services such as COM components, Dynamic HTML, Web browser and server, scripting, transactions, message queuing, security, directory, database and data access, systems management, and user interface. These various interfaces are all exposed in a uniform manner at all tiers of a given application. |
| IrisLogic can build robust, scalable, multi-tier business applications and deliver them over any network architecture. By using the Windows DNA architecture, applications are dynamic, flexible, scalable, and can be easily adapted to accommodate changing business needs. |
| Windows DNA is built upon components and transactions, two fundamental concepts of application development. |
| Components |
| Software components are self-contained units of run-time code that provide specific functionality for an application. A component architecture provides the following benefits: |
 |
Reusability- a component can be re-used once it is created, which allows for multiple applications to rely on a single piece of code without having to rewrite its functionality. |
|
Reduce complexity - other developers need only to know what information to provide to the component and what information to retrieve. |
|
Easier to update - in effect, updating a single component updates the entire application. |
|
Easier to develop - separating the code into small, discrete components allows for easier testing and assigning programming chores among developers. |
|
Language neutrality - components can interact regardless of the original language code. |
|
| |
| In the IrisLogic Microsoft Framework, component architecture is implemented in the Component Object Model (COM) or the Distributed Component Object Model (DCOM). |
|
| The Three-Tier Application model is courtesy of Microsoft© Corporation. |
| Transactions |
| Work completed in a database or message queue often involves a great number of concurrent users with constant change to the data source tables. An application must be able to handle situations where some objects fail. Transactions provide for a simple all-or-nothing model of managing work. Either the object succeeds and all the work is committed, or the object fails and none of the work is committed. |
| Transactions offer a fault tolerant service for a set of computing resources and form an essential element for enterprise-level distributed applications. |
| |
| Microsoft Solutions |
|
