Imagine software that could run on EVs, Powerwall-type batteries, computers/tablets/smartphones, and so on, which would automatically charge and discharge for passive income. Essentially algorithmic trading, but with power instead of stock. You'd just have to configure any necessary time ranges and charge percentages, e.g. maybe your EV needs to be at 25% by 8am and again by 5pm on weekdays in order to make your daily commute.
Maybe some EVs will start to come with built-in crypto miners to burn negatively priced power when the battery is at capacity. Maybe Lyft/Uber and Waymo/Cruise will take advantage of it by increasing and lowering rates based on the price of power (if they don't already).
I’ve been pushing the use of Datadog for years but their pricing is out of control for anyone between mid size company and large enterprises. So as years passed and OpenTelemetry API’s and SDK’s stabilized it became our standard for application observability.
To be honest the documentation could be better overall and the onboarding docs differ per programming language, which is not ideal.
My current team is on a NodeJS/Typescript stack and we’ve created a set of packages and an example Grafana stack to get started with OpenTelemetry real quick. Maybe it’s useful to anyone here: https://github.com/zonneplan/open-telemetry-js
There must be an easier way to write migrations for pgroll though. I mean, JSON, really?
Of course there are a multitude of variables we don't have access from the outside, but Postgres only compresses data that is TOASTed, and based on your description of the table, the data is not being TOASTed (and therefore not being compressed).
Instead, if you could somehow pack your timeseries entries into an array, you would get the benefits of compression automatically.
Given your write performance requirements, using an array may be out-of-question (and you may get too much overhead from dead tuples) -- but who knows? Always a good idea to benchmark.
I actually considered mentioning this at the post but figured it was too long already and could be the material for a future one :)