At StackGres [1] we find Timescale to be one of the most used extensions. Timescale is quite a successful project!
StackGres is actually the first solution recommended by Timescale for self-hosting with Kubernetes operators [2].
So if you are into Kubernetes (or if not, consider it, using something like K3s [3] is quite straightforward and lightweight on resources), this is probably a great option to self-host which would avoid you all the hassle of manually doing all the setup involved for production-ready clusters.
I run it on VM the same way as a few separate PostgreSQL instances.
TimescaleDB is an extension to PostgreSQL, so there's a lot of information, guides, and community support online, and Postgres is one of the most widely used databases right now. There are some things to setup but Tiger data documentation is very good.
I've tested the migration of the main table (IoT data), from 300GB to about 25GB in a non-production environment. Everything seems right, but I'm still delaying/procrastinating the prod migration, so I wanted to know how it is going for other live projects.
StackGres is actually the first solution recommended by Timescale for self-hosting with Kubernetes operators [2].
So if you are into Kubernetes (or if not, consider it, using something like K3s [3] is quite straightforward and lightweight on resources), this is probably a great option to self-host which would avoid you all the hassle of manually doing all the setup involved for production-ready clusters.
[1] https://stackgres.io
[2] https://www.tigerdata.com/docs/get-started/choose-your-path/...
[3] https://k3s.io/