Many TSDBs offer specialized advantages:
* need fast append-only changes? influxdb covers that
* need performance for short-term time-series data? go for Prometheus
* most TSDBs offer compression to the data stored. In TSDBs, especially the timestamps, can be highly efficiently compressed. Some TSDBs (Chronix[0], for example) even offers an option to completely drop the timestamps in exchange for space savings. E.g., in Chronix's home page, they listed: The dataset contains about 3.7 billion pairs and takes 108 GB serialized as CSV. Chronix needs only 8.7 GB to store the dataset.
* high-level analytics that only makes sense for time-series data. Chronix[0], again for example, offers a list of high-level functions[1], such as derivatives, integrals, frequency, scaling, or even SAX. Note that you could implement in SQL Server, but would be a huge pain. It's really great that you could push these to the database layer.
(I'm not affiliated with Chrnoix in any way, I just happen to be a very happy user in my recent project. You can see a review of Chronix by Adrian Colyer in [3])
[0]: https://github.com/ChronixDB/chronix.server
[1]: https://github.com/ChronixDB/chronix.server#function-query
[3]: https://blog.acolyer.org/2017/03/10/chronix-long-term-storag...
The most interesting thing about Chronix, to me, seems to be data size ( would be interesting to see what the performance is like too ). I think I'll do an experiment and spit a bunch of data into it and see how it does.
"Due to problems in previous seminars, we will not be allowing therapy snakes into the room anymore. Thank you for your cooperation."
Is that an inside joke or is there a snake story somewhere?
I took 2 databases courses organized by Stan and Andy, like his adviser, Andy was very good at explaining complicated things in layman terms.
