5 ms·

Using the FDAP Architecture to Build InfluxDB 3.0: Flight, DataFusion, Arrow

somedude82 3y ago
Yet another "NEW TECH" craze from InfluxDB. All their marketing is the same - always - look we use something new. Every 2-3 years the same. I am waiting for InfluxDB 4.0 when Rust hype ends and Zig/OCaml or whatever is the new hype. p.s. https://news.ycombinator.com/item?id=37614611 https://news.ycombinator.com/item?id=37614611 p.s.s. please build something that is not going to be deprecated in 3 years. DB world does not need this fruitfly lifetime nonsense. I can no build my things on these promises.
- cjalmeida 3y ago
  I actually read this as the opposite of NEW TECH craze. The components are commonly used in the data community, despite being cutting edge. The only exception might be DataFusion as it's hard to play against Spark/Databricks push in distributed computing for data.
  - somedude82 3y ago
    look at InfluxData history. If this seed round funds run out there will be push for 4.0 and this will be whatever attracts investors money
- lawn 3y ago
  I use InfluxDB 2.0 with Home Assistant and Grafana, but I'm not really happy. The Grafana integration feels half-finished, with multiple things that are unsupported or breaks. Even simple things like rewriting labels may require undocumented and hacky workarounds. I wish they would polish what they have instead of jumping to the next shiny thing (and breaking the previous version).
- deleted 3y ago
  [deleted]
exabrial 3y ago
Influx: Please, just pick up Kapacitor 1.x and Chronograf 1.x and work on the TICK stack. You really had something going and you abandoned it for shiny toys.
- justin_oaks 3y ago
  I used Kapacitor 1.x and Chronograf 1.x for a couple years. I found TICKscript to be confusing, underdocumented, and a pain to manage. I thought Chronograf was OK. I switched to Grafana for both alerts and data visualization and everything is just better than what I had with Kapacitor and Grafana. Kapacitor seemed to use a lot more CPU power, but that may be because data is streamed to it instead of periodically queried. What is it about those two products that you like enough to keep using them or wanting them to be developed?
mehdix 3y ago
I was on Influxdb 1.8 when they introduced 2.0 and flux. I'm glad I refused to switch since it's deprecated in 3.0.

Yet another "NEW TECH" craze from InfluxDB. All their marketing is the same - always - look we use something new. Every 2-3 years the same. I am waiting for InfluxDB 4.0 when Rust hype ends and Zig/OCaml or whatever is the new hype. p.s. https://news.ycombinator.com/item?id=37614611 https://news.ycombinator.com/item?id=37614611 p.s.s. please build something that is not going to be deprecated in 3 years. DB world does not need this fruitfly lifetime nonsense. I can no build my things on these promises.

cjalmeida 3y ago
I actually read this as the opposite of NEW TECH craze. The components are commonly used in the data community, despite being cutting edge. The only exception might be DataFusion as it's hard to play against Spark/Databricks push in distributed computing for data.
- somedude82 3y ago
  look at InfluxData history. If this seed round funds run out there will be push for 4.0 and this will be whatever attracts investors money
lawn 3y ago
I use InfluxDB 2.0 with Home Assistant and Grafana, but I'm not really happy. The Grafana integration feels half-finished, with multiple things that are unsupported or breaks. Even simple things like rewriting labels may require undocumented and hacky workarounds. I wish they would polish what they have instead of jumping to the next shiny thing (and breaking the previous version).
deleted 3y ago
[deleted]

exabrial 3y ago

Influx: Please, just pick up Kapacitor 1.x and Chronograf 1.x and work on the TICK stack. You really had something going and you abandoned it for shiny toys.

justin_oaks 3y ago
I used Kapacitor 1.x and Chronograf 1.x for a couple years. I found TICKscript to be confusing, underdocumented, and a pain to manage. I thought Chronograf was OK. I switched to Grafana for both alerts and data visualization and everything is just better than what I had with Kapacitor and Grafana. Kapacitor seemed to use a lot more CPU power, but that may be because data is streamed to it instead of periodically queried. What is it about those two products that you like enough to keep using them or wanting them to be developed?

mehdix 3y ago

I was on Influxdb 1.8 when they introduced 2.0 and flux. I'm glad I refused to switch since it's deprecated in 3.0.