dassana VS QuestDB

couldn't agree more- we built Dassana [1] so solve this problem by adding context to security alerts. Currently we support AWS Config/GuardDuty alerts but had been thinking of adding context to vuln scan results too.

[1] https://oss.dassana.io/

Dassana | all things backend/cloud/data | San Jose (CA) | Full Time | https://oss.dassana.io/

Dassana is an open source cloud security company on a mission to alert fatigue problem. The start-up is well funded and founders are serial entrepreneurs. This is a founding engineer role who will lead all architecture, design, deployment, monitoring efforts of the SaaS service we are starting to build. If you ever wanted to build a large scale SaaS service from ground up, this is the place for you. We don't care if you are a java or python or go person. We care that you find the tool which fits the problem and not the other way around.

We do things differently here, and that starts with four day work week. Your contributions will make internet a safer place. Come, join the mission.

email- gk at dassana dot io

If your data lacks uniform time intervals between consecutive entries, QuestDB offers a solution by allowing you to sample your data. After that, MindsDB facilitates creating, training, and deploying your time-series models.

If you're interested in that functionality or have any other feedback, please drop by our open source repository or community Slack and let us know.

QuestDB is a high-performance time series database with SQL analytics that can power through market data ingestion and analysis. It's open source and integrates well with the tools and languages you use. Check us out!

Looks like full keys are always compared if hash codes test equal, which is what I'd expect. For example: https://github.com/questdb/questdb/blob/master/core/src/main...

But of course, I want to run a QuestDB instance on my node, which uses two additional TCP ports for Influx Line Protocol (ILP) and Pgwire communication with the database. So how can I expose these extra ports on my node and route traffic to the QuestDB container running inside of k3s?

In this post, I will detail a way in which I recently used annotations while writing an operator for my company's product, QuestDB. Hopefully this will give you an idea of how you can incorporate annotations into your own operators to harness their full potential.

QuestDB is an open source, high performance time series database. With its massive ingestion throughput speeds and cost effective operation, QuestDB reduces infrastructure costs and helps you overcome tricky ingestion bottlenecks. Thanks for reading!