sman393

I have to disagree with that, I've found GCP docs to be much more informative and easier to digest.

Not sure what you mean about a lack of human support, but i've had a great experience with their support team so far if it was ever needed.

Depending on what your reporting needs are I would definitely recommend TimescaleDB. I love Prometheus for storing server resource metrics or basic app metrics (counts/timers). For more business-facing data, having the query functionality and visualization tooling of Postgres is a major win. I am working on a similar use-case to you, we considered Cassandra, Timescale, and Clickhouse. With our insert rates and reporting needs, We decided to start working with TimescaleDB.

That could be a great idea, luckily the path train exists, although I've never commuted on it so I can't speak to its reliability.

This is a great idea

"Northeast Philly is the new Williamsburg"

That's a bit of a stretch...

Alright thanks! I thought I read that TimescaleDB doesn't support clustering yet, only single node Postgres installs, But I could've misunderstood it.

Good to hear! how does the current TimescaleDB single node limitation play into it?

Can this be used side by side on normal Postgres cluster? As in could I have one DB for app data, and one for metrics data? Considering switching from MySQL (ndb cluster) to running a Postgres cluster and this could be a good motivator.

Agreed! It's a great service, with quality content.