Hi Committers

I have thought about this discussion and vote for months. Also,
several people asked me about this dozens of times.
InfluxDB 1.x and IoTDB plugins exist for years and months, I noticed
there are several issues.

InfluxDB faced serious performance impact when it is used in
collecting/query traces and logs. Mostly due to trace ID making too
many candidates for query index, which is not expected/designed in
this kind of database.
IoTDB has no feedback since it is added. We need to consider
maintenance payload in months.
Every time when we need to update the core, we have to take care of
InfluxDB and IoTDB implementations, including e2e tests and inside
logic.

In the SkyWalking community, we follow the principle, (mutable) core
features should have stable committers to keep eyes on it, also, they
should have stable feedback from the community. AFAIK, I don't think
both of these features reach this standard.

So, I am initializing this discussion as well as voting, we should
consider removing both of these options.

Please feedback here
https://github.com/apache/skywalking/discussions/9059, or in this mail
thread.

Sheng Wu 吴晟
Twitter, wusheng1108

Reply via email to