We’re on azure and a surprisingly good choice has been to use their eventhub to ingest the telemtry and then to consume it in batches of a few seconds using a consumer. Time series is hard because it is a lot of data that comes in all the time, this allows you to relax those requirements a bit.
After eventhub we’re using ducklake. But I’m not at the point where I’d flat out advise it to other people (just code immaturity that tk their credit is being worked on)
Also, if you’re evaluating postgres, check out timescaledb.
We’re on azure and a surprisingly good choice has been to use their eventhub to ingest the telemtry and then to consume it in batches of a few seconds using a consumer. Time series is hard because it is a lot of data that comes in all the time, this allows you to relax those requirements a bit.
After eventhub we’re using ducklake. But I’m not at the point where I’d flat out advise it to other people (just code immaturity that tk their credit is being worked on)
Also, if you’re evaluating postgres, check out timescaledb.