Introduction

PowerServer deployments are different from traditional PowerBuilder client/server application deployments in the following ways:

During the PowerServer project compilation and deployments:

  • All DataWindows/DataStores are automatically converted to .NET models, and then automatically exposed via REST/JSON APIs;

  • All embedded SQLs will be deployed to the server side, and then automatically exposed via REST/JSON APIs;

  • All PBD files are broken down very granularly into each individual object/definition file.

When an end user starts an installable cloud app for the first time:

  • Each client must download and install a supporting program, Cloud App Launcher, and also download the supporting runtime files;

  • Each client will download the app files from the web server. There are two possible ways: Download the app files as necessary, or download all the app files at app startup.

  • It is possible that some preload event (e.g., commands for environment detection or control registration) shall be executed before the app starts.

When an installable cloud app starts to run:

  • The app has no dependency on a web browser (type, version, or settings), and will run and update itself as needed over the Internet;

  • The app runs in a web or cloud environment instead of the previous on-premise environment. It is powered by REST APIs that interface with the data sources, and such REST APIs is hosted in PowerServer in a public or private cloud.

Due to the above differences, it can be well expected that the relevant performance behavior will be different from the client/server applications. This document will provide you some common performance tuning techniques to get maximum performance out of the PowerServer project development and implementation.