velero-plugin-for-gcp
QuestDB
| velero-plugin-for-gcp | QuestDB | |
|---|---|---|
| 1 | 311 | |
| 72 | 13,475 | |
| - | 0.7% | |
| 6.9 | 9.7 | |
| 10 days ago | 7 days ago | |
| Go | Java | |
| Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
velero-plugin-for-gcp
-
Running QuestDB on GKE Autopilot
Set permissions for Velero
QuestDB
-
How to Forecast Air Temperatures with AI + IoT Sensor Data
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.
-
Normalizing Grafana charts with window functions
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.
-
How to increase Grafana refresh rate frequency
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!
-
Building a faster hash table for high performance SQL joins
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...
-
K3s Traefik Ingress - configured for your homelab!
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?
-
Annotations in Kubernetes Operator Design
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.
-
Is all data time-series data?
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!
- questdb: NEW Data - star count:12960.0
What are some alternatives?
velero - Backup and migrate Kubernetes applications and their persistent volumes
TDengine - TDengine is an open source, high-performance, cloud native time-series database optimized for Internet of Things (IoT), Connected Cars, Industrial IoT and DevOps.
velero-plugin-for-aws - Plugins to support Velero on AWS
arctic - High performance datastore for time series and tick data
k8s-gitops - GitOps principles to define kubernetes cluster state via code
ClickHouse - ClickHouse® is a free analytics DBMS for big data
velero-plugin-for-openstack - Openstack Cinder, Manila and Swift plugin for Velero backups
SQLAlchemy - The Database Toolkit for Python
VictoriaMetrics - VictoriaMetrics: fast, cost-effective monitoring solution and time series database
tsbs - Time Series Benchmark Suite, a tool for comparing and evaluating databases for time series data
Metabase - The simplest, fastest way to get business intelligence and analytics to everyone in your company :yum:
Grafana - The open and composable observability and data visualization platform. Visualize metrics, logs, and traces from multiple sources like Prometheus, Loki, Elasticsearch, InfluxDB, Postgres and many more.