Don't blame the developer advocate for the company's mistakes. Developer advocates rarely have any part in these kinds of decisions, but are left holding the bag whenever they go badly.
The original TSM engine is still used by InfluxDB v2 OSS.
The InfluxDB Cloud platform uses a variation of TSM that's tailored for a distributed SaaS rather than stand-alone nodes (this was originally intended to be used in InfluxDB v2 OSS as well, but alpha-testing showed that the old engine performed better there so it ultimately was reverted for the beta release).
So IOx is really the first major new storage engine in InfluxDB.
So many things are qualitative, but not quantitative. They can be measured, but not counted. Happiness is one of those, you can say that you are "more happy" or "less happy" from one day to the next, but you can't count happiness, you can't put a number on it.
I'd recommend reading The Community Engagement Trap[0] by Rosie Sherry (which should also be shared here on HN), she talks about Community Discovery as the process for getting these deeper understandings.
A user's engagement with your product is a great metric, because what you value is users using your product.
But for a COMMUNITY it's the wrong metric, because you don't value negative comments in your Slack no matter how many there are (in fact, the more there are the worse it is).
