santafen

Yes, it's alpha, but ...

This is like telling someone in Marketing "recompiling the linux kernel and turning on some new drivers is really simple. You don't even need to understand kernel architecture to do that."

Yes, it's simple for you, but for folks who just want to make sure that all their QR Codes reflect their brand, having to recreate that every time isn't worth it.

It's fine if this isn't your cup of tea.

Thanks for your helpful input.

It's the ability to customize the codes that you're paying for. Ad logos, and an almost limitless amount of customization. If all you want is standard black and white squares, that's easy and free all over the place.

These codes will never expire. Unlimited scans.

There's a tutorial (mini-tutorial really) that goes along with that. https://docs.otterize.com/quick-tutorials/aws-eks-cni-mini

How often do people take a family of six grocery shopping? On vacation, sure, but that's an entirely different use model.

I'm 100% here for station wagons!

You could have just responded with ¯\_(ツ)_/¯ and saved a lot of typing.

I've actually been looking for a comprehensive and detailed comparison of Clickhouse vs Pinot, so this is timely for me. I like that this article has some easy to digest lists of what is supported in each implementation, but that's fairly high-level. The deeper dives into features and specific use cases was much more helpful.

Head of DevRel for QuestDB here drop me an email at davidgs(at)questdb(dot)io and I'll make sure you get invited.

Thank so much!

Thanks!

I don’t think it’s being downvoted. Maybe it’s because it’s an actual post?

When I ran it it took about 20s total.

Great question! Time series databases are a great solution for applications that need to process streams of data. IoT is a popular use case. DevOps and infrastructure monitoring applications as well. As has been mentioned in other comments here, there are a lot of use cases in financial services as well.

These are all applications where you’re dealing with streams of time-stamped data that needs to be ingested, stored, and queried in huge volumes.

Thanks for the kind words!

Thanks for the helpful feedback! Feel free to reach out to chat more. I'm super interested in more feedback from you. davidgs(at)questdb(dot)io

No one is allowed to benchmark them except them. :-)

Some of those are absolutely monstrous tips!

QuestDB Head of DevRel here ... Yes, it can be a replacement of Postgres and it will be cheaper and faster. That being said, PGwire is still in alpha and is not 100% covered yet, so while migrating is possible, 100% Postgres Wire Protocol compatibility is not there yet.

For traditional transactional RDBMS data, I don't think it's a very common choice. For Time Series data, QuestDB is by far the fastest choice for Postgres-compatible SQL Time Series databases.

Here's a Medium post on Time Series Databases: https://medium.com/datadriveninvestor/what-are-time-series-d... But basically, they are databases where the time dimension is a critical aspect of the data. They handle never-ending streams of incoming time-stamped data. Think of streaming stock prices, or streaming temperature data from a sensor. You want to be able to query your data specifically in a time dimension -- let's see the temperature fluctuations over the past 24 hours, including the mean. Stuff like that.

A 'normal one' is typically used for things like transactional data which adds, deletes, and updates data among linked tables. While these transactions happen in time, the time component isn't necessarily a critical dimension of the data.

¯\_(ツ)_/¯ Influx laid off pretty much the entire DevRel team in the last 6 months, but ok.

This was from the CTO last week: "This work won't be landing anywhere until sometime next year and it'll be landing in our Cloud 2 offering first." So the OSS is definitely a second-class citizen. And now that they've dropped all DevRel activity, don't expect much attention for OSS Developers and users.

As someone else pointed out, and a QuestDB engineer responded, it’s been noted and an issue has been created for it. 5e reasoning for it was actually solid.