Discover and read the best of Twitter Threads about #InfluxDB
Most recents (3)
Today is a big day @InfluxDB. We're announcing the release of InfluxDB IOx, the new core of the database written in #rustlang and built with @ApacheArrow. It delivers infinite cardinality, tiered data storage, SQL compatibility and so much more. Here's some of the background...
When we released #InfluxDB 1.0 in 2016, it was written in #golang and had a custom storage engine we built from scratch that was specifically optimized for metrics workloads. We called it the Time Structured Merge Tree (or TSM for short).
The design of TSM paired a time series storage database with an inverted index to map metadata to underlying time series. This delivered excellent performance for low to medium cardinality workloads. But as the precision of information in the metadata increased, the DB suffered.
Choosing the right tech stack is one of the most important decisions when building a software product.
The ability to scale quickly depends on many factors but having the proper tech stack may be the most important one.
(Thread) 👇
The ability to scale quickly depends on many factors but having the proper tech stack may be the most important one.
(Thread) 👇
1/ Tech stacks not only impacts the scalability in terms of performance but also provides flexibility and agility to evolve the product, eases the development of ecosystems, and attracts and retains talent.
2/ I am sharing in this thread, some of the components of our tech stack at @intraway that are working great for us.
Let's go over each mistake [thread]
The "scan" template variable was an earlier attempt to solve the problem of not being able to use timeFilter, to, or from variables inside other template variables. The user would have to select a scan value to modify the other template variable scan range 
