4 ms·
TimescaleDB (single-node) leverages Postgres features for HA (physical replication). It was never in the "enterprise tier", it fully works with the pure Apache
by mfreed 6y ago
TimescaleDB (single-node) leverages Postgres features for HA (physical replication). It was never in the "enterprise tier", it fully works with the pure Apache 2 version.
We also make available k8s helm charts that make it super easy to setup replicated clusters, including with mechanisms (Patroni) for automated failure detection and failover, and continuous incremental backup. That's also available under the Apache-2 license:
https://github.com/timescale/timescaledb-kubernetes https://github.com/timescale/timescaledb-kubernetes
(There used to be some slightly confusing language in our product page that perhaps led to some of your confusion, and apologies for that.)
For multi-node (available starting in TimescaleDB 2.0), we are working on more native mechanisms for replication. But as announced earlier, these will all be "community" features (free) under our Timescale License.
- jjjensen90 6y agoI've commented on it before, but I have to say again, the Timescale Helm charts are by far the best way I've ever seen a database run in Kubernetes, and actually from an operations, backup, and scaling perspective they are the best database management experience I've had period. Huge fan, always enjoy talking with Feike, and keep up the great work Timescale team.
- Drdrdrq 6y agoGreat job on the product! I was also very impressed with the support on slack channel, you guys rock! One thing that I found confusing is that there is no clear explanation of the differences between the editions. Your answers are very clear and explain things nicely, but I would expect this information to be available on your site. Just a thumbs up. Keep up the good work!
- mosselman 6y agoSounds great thank you. Are there any docs on non-k8s setups? Maybe with docker-compose?