PoWA Deployment Models

PoWA supports local and remote deployment. For details, see Local Deployment and Remote Deployment. For security purposes, RDS for PostgreSQL supports only remote deployment of PoWA.

Local Deployment

The architecture is simple and does not require the participation of the PoWA-collector. It consists of only the PoWA-archivist, PoWA-web, and other plug-ins. However, this architecture has the following disadvantages:

It increases performance costs when collecting data and using the user interface.
Collected performance metric data is stored on the local host, which increases the disk space usage.
Data cannot be collected on the hot standby server.

For security purposes, RDS for PostgreSQL does not support local deployment.

Figure 1 Local deployment architecture

Remote Deployment

PoWA 4.0 allows you to store the data of one or multiples servers on an external PostgreSQL database. Currently, RDS for PostgreSQL supports PoWA 4.1.2.

Compared with local deployment, remote deployment has a dedicated Powa repository database for storing performance metric data collected by PoWA-collector.

RDS for PostgreSQL supports remote deployment.

The remote deployment architecture is as follows.

Figure 2 Remote deployment architecture