NodeChef PostgreSQL Hosting

Deploying a PostgreSQL server to NodeChef bare metal cloud platform is as simple as providing a name for your deployment, select a region and clicking a deploy button.

The NodeChef platform takes care of the server setup, container orchestration and automatic fail-over to hot standbys. With a simple web interface, you can deploy, link your App instances in a few clicks.

NodeChef bridges the gap between fortune 100 companies that can afford to run and manage an in-house dedicated infrastructure and small and mid sized businesses that seek dedicated hosting at an affordable price.

NodeChef managed bare metal cloud is more affordable and also outperforms VPS hosting and can save you tons of work configuring, managing and monitoring your PostgreSQL server.

NodeChef PostgreSQL deployments allow developers to focus on what they do best (developing applications) and avoid the guesswork of capacity planning. Your deployment autoscales without any downtime to accomodate your workloads. In addition to autoscaling, PostgreSQL deployments include built-in hot backups every 24 hours and continuous WAL segment archiving and point in time (PITR) database restore. Backups and WAL segments can also be archived to your own S3 bucket.


NodeChef currently uses PostgreSQL Server version 9.6. The POSTGIS extension is enabled by default.

Postgres Monitoring

Architecture

Each PostgreSQL node in the cluster consists of the PostgreSQL server and three independent cluster monitoring nodes.


Layer Role
PostgreSQL Servers Master and standby servers supports SSL encryption and md5 password authentication access by default. Replication from master to standby servers also enforces md5 authentication. IP whitelisting can be enabled from the dashboard if required.
Monitor nodes 3 independent nodes responsible for monitoring the state of the PostgreSQL Cluster. If the master node fails, one of the monitor nodes initiates the process to promote a standby to the role of a master node. The monitoring nodes are only enabled for High Availability deployments. If you only deploy a single node without replication, the monitor nodes are not activated.