PostgreSQL on Hikube
Hikube offers a managed PostgreSQL service. The platform handles the deployment and management of a replicated, self-healing PostgreSQL cluster, which you create and manage from the Hikube console (DB & Messaging → PostgreSQL menu).
Architecture and operation
The platform automates the database lifecycle: creation, updates, replication and incident recovery.
The architecture is built around a replicated cluster:
- A primary node that handles writes and serves as the reference for data consistency.
- One or more replicas (standby) that continuously receive changes through replication.
- An auto-failover mechanism that automatically promotes a replica to new primary in the event of a failure, with no manual intervention.
This approach ensures:
- Resilience against hardware or software failures
- Read scalability by distributing queries across replicas
- Operational simplicity, as the platform handles cluster coordination and maintenance
What you manage from the console
| Feature | Available |
|---|---|
| Cluster creation (version 15 to 18, preset, disk size, 1 to 3 replicas, external access) | Yes |
| Databases and PostgreSQL extensions | Yes |
| Users, per-database rights (admin / read-only), password rotation | Yes |
| Version upgrade, preset change, disk size increase, change of external access | Yes |
| Cluster restart | Yes |
| Changing the number of replicas after creation | No, contact support |
| Scheduled or on-demand backups, restore (including to a point in time) | Yes, Backups tab (see Backups) |
Use cases
- Business-critical applications requiring a reliable, highly available database
- E-commerce and ERP, where service continuity is essential
- Multi-tenant SaaS, distributing load between the primary and replicas
- Business Intelligence and reporting, thanks to optimized reads on replicas
- Cloud-native applications, deployed on your Hikube Kubernetes clusters