cockroach VS InfluxDB

You absolutely can write very high performance software in Go, that's kind of the point. You can efficiently interface with C libraries. You can create the sort of software everyone says should be done in Rust, like databases and web servers and system orchestration and games and every other goddamn thing that people will say isn't the right choice for Go.

PostgreSQL Parser separated from CockroachDB, a distributed DB.

Spencer Kimball (now CEO at CockroachDB) wrote an interesting article on this topic in 2021 where they created spencerkimball/stargazers based on a Python script. So I started thinking: could I create a data pipeline using Nifi and Kafka (two OSS tools often used with Druid) to get the API data into Druid - and then use SQL to do the analytics? The answer was yes! And I have documented the outcome below. Here’s my analytical pipeline for Github stars data using Nifi, Kafka and Druid.

One of the most popular distributed DB is built in Go: https://www.cockroachlabs.com/

Recently, I worked on such an integration with Splunk. The Splunk dashboard files that emulate the DB Console are now available in our repo for everyone's benefit.

Technically not postgres, but could be worth checking out cockroach db, it can use any postgres driver from programming languages and is build for distribution. I recently moved from postgres to cockroach (with golang postgres driver) and didnt need to change a single query

And InfluxDB Github commit history histogram is telling its story https://github.com/influxdata/influxdb/graphs/contributors

We have 40+ InfluxDB servers (for iot sensor data) but I think in couple of years we will move to TimescaleDB. InfluxDB problem is their company InfluxData that has pivoted away from InfluxDB after v2 release and tried their Rust thing (IOx) and now is promoting their Telegraf. For me this is a sign of no clear vision from company. I can not trust my database to company that will probably abandon InfluxDB in couple of year. Just look commit histogram https://github.com/influxdata/influxdb/graphs/contributors After their released InfluxDB is run on skeleton crew. Also see https://news.ycombinator.com/item?id=23906592

InfluxDB

I figured, if I'm storing time-series data, it makes sense to use a popular open-source solution that's optimized exactly for that. In this article, I'm going to show you how I tied in the time-series database InfluxDB into my existing Laravel application. After doing this, not only have my response times improved drastically, but the database size has shrunk considerably as well.

Their licence policy may be hard to find on their website, but you can find it elsewhere easily, i.e. github: https://github.com/influxdata/influxdb/blob/master/LICENSE

I would suggest using something better suited to IoT data than ... a spreadsheet. I'd recommend looking at one of the Time Series Databases for this. 1) QuestDB or 2) InfluxDB as these are much better suited to streaming data.

No, not really.