Building Distributed
Applications
Using the Progress AppServer
Conditions That Make Migrating Your Application Model Easier
Certain conditions related to your current application framework allow you to more easily take advantage of Progress AppServer functionality. These conditions include any of the following:
- Your present server has adequate resources such as memory, speed, and disk space to be easily scaled up for use with the Progress AppServer.
- Your current model has a predominance of small, well-structured, identifiable transactions. The Progress AppServer favors a small transaction model. For more information, see the "Transaction and Record Management Considerations" section.
- You are already using temporary tables to manipulate data before committing the data to the database. Or, if you are not using temporary tables, it is easy to get your present code to work with temporary tables rather than deal directly with your database.
- Your current model is already set up such that neither procedures nor persistent procedures rely on shared/global data or buffers as parameters. These types of information cannot be shared between a client application and an Application Server process.
- Your current model already has a distinct division between the logic associated with the user interface and the logic associated with your application. This enables your code to be modular and portable, in keeping with how you will want your code to be deployed in a distributed environment using the Progress AppServer<$startrange>Design and implementation:designing your distributed application model.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |