|
|
|
|
|
by mfreed
2153 days ago
|
|
Hey, thanks for the continued discussion: > If there is some kind of emergency and I need to have
> the database on the cloud, this is a serious restriction.
> It limits my choices and constrains my actions.
> if the license change to allow me to deploy to a cluster
> of AWS servers (just in case we ditch our own hardawre),
You can deploy TimescaleDB on AWS servers (the TSL certainly allows it). Most of our users do. They don't run their own hardware.You can even use our Apache-2 k8s helm charts [1] to immediately spin up a cluster of replicated TimescaleDB nodes with automated leader-election/failover and continuous incremental backup. The helm charts have first-class support for AWS EKS. What the TSL prevents is _Amazon_ offering TimescaleDB as a paid DBaaS service. To my knowledge, none of the major cloud vendors offer Clickhouse as a first-class paid service, so that's somewhat a moot point. I guess theoretically Amazon could launch Clickhouse-as-a-service, but that theoretical possibility doesn't help you in your emergency. [1] https://github.com/timescale/timescaledb-kubernetes |
|