Secure, Supported and Enterprise-Ready
Postgres Plus Cloud Database (PPCD) meets the most demanding needs of enterprise-class applications with a rich feature set, elastic scalability, and reliable high availability, all available at your fingertips with an easy-to-use dashboard. Drive your web business's financial transactions, catalog sales, or customer business intelligence. Quickly set up and take down standard development, test, and deployment environments. Support diverse database workloads including ACID-compliant relational information, and built-in NoSQL document and key-value datatypes — all in one database available in the cloud as well as on-premises.
How It Works
The Postgres Plus Cloud Database console is used to deploy Postgres databases to Cloud server instances. The first database deployed to an instance becomes the master database. If replica instances are selected, they will be created in a cluster with the master database.
The master database, all replica instances, and Amazon storage for the database all exist in your AWS account, while Postgres Plus Cloud Database consoles are owned and operated by EnterpriseDB.
|The architecture of the
showing the console
managing a database
cluster by using
and showing how
the database cluster.
Each database cluster includes a load balancer to which applications may connect. The load balancer receives incoming requests from applications and distributes read requests across all read-only replicas within the cluster (unless there are no replicas, in which case the master handles all requests). Write requests are passed directly to the master database.
From an application's perspective, connecting to a PostgreSQL or Postgres Plus Advanced Server instance that resides in the cloud is no different than connecting to an instance that resides on traditional hardware.
|Steps performed to manage failover of a master database server in a database cluster.|
When it initially connects to the Postgres database, the application authenticates itself with the server using a role defined when the server cluster was created. All IDE and development tools can connect directly to the database by using the address and port information provided when the cluster was created.
Automatic failover minimizes data loss and downtime. Should a server failure occur, two failover modes serve your needs unattended. "Transaction preferred" to prevent data loss, or "recovery preferred" to be back online as fast as possible.
A storage Logical Volume Manager (LVM) aggregates storage to scale storage up without interrupting the operation of running applications. When you provision your database, you can choose to have stored data encrypted.
A Logical Volume Manager (LVM) aggregates storage for the cluster, facilitating transparent scaling of cloud storage without adversely affecting running databases.
All database deployments use private instances that are never shared with other customers. Not only does this improve security and stabilize performance, but also allows you to treat your databases as your own — making whatever configuration or operational changes you require.