clickhouse-operator
vitess
| clickhouse-operator | vitess | |
|---|---|---|
| 5 | 60 | |
| 1,730 | 17,834 | |
| 1.8% | 0.7% | |
| 9.8 | 9.9 | |
| 7 days ago | 7 days ago | |
| Go | Go | |
| 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.
clickhouse-operator
-
ClickHouse Cloud is now in Public Beta
but this pricing looks excessive.
A single node instance with a fast disk is more than sufficient for most needs: https://hub.docker.com/r/clickhouse/clickhouse-server
If you need a cluster, https://github.com/Altinity/clickhouse-operator makes things easy
-
Databases in 2021: A Year in Review
Altinity is doing a good job of this with Clickhouse. They offer some decent open source guides for self hosting[0] and offer a hosted option. The hosted option is as self serve as I'd like (you have to get "approved").
0 - https://github.com/Altinity/clickhouse-operator and
-
Show HN: Distributed Tracing Using OpenTelemetry and ClickHouse
Where is the clickhouse data stored, in the Docker container?
For reference, here's what I'm using: https://github.com/Altinity/clickhouse-operator/blob/master/...
-
What's New in ClickHouse 21.12
ClickHouse works great on Kubernetes. Check out the ClickHouse Operator for Kubernetes. [0] We just added a UI to it, blog article out shortly.
[0] https://github.com/Altinity/clickhouse-operator
Disclaimer: I work at Altinity.
-
What is ClickHouse how it compares to PostgreSQL and TimescaleDB for time series
Don't use helm. The ClickHouse Kubernetes Operator is the way to go. Here's the project: https://github.com/Altinity/clickhouse-operator
This is generally true for most databases these days. Use an operator if it's available. Helm can't handle the dynamic management required to run databases properly.
vitess
-
A MySQL compatible database engine written in pure Go
With Vitess likely merging a lot of its binaries into a single unified binary: https://github.com/vitessio/vitess/issues/7471#issuecomment-...
... it would be a wild future if Vitess replaced the underlying MySQL engine with this as long as the performance is good enough.
-
The challenges of supporting foreign key constraints
Thank you for the compliment!
We recently started adding support for CTEs in Vitess! You can check out https://github.com/vitessio/vitess/pull/14321 if you want to see some technical details of the implementation.
For now, we have added preliminary support by converting them to derived tables internally, but we believe that we need to make CTEs first-class citizens themselves of query planning. Once we make that change, we can look towards supporting recursive CTEs.
This however will take some time, but then, all good things do!
-
Vitess 18
Why would it be a Google project? https://github.com/vitessio/vitess
-
PlanetScale Scaler Pro
This is great news. I strolled around https://github.com/vitessio/vitess/issues/12967.
Are there any public discussions of more trade-offs vitess has to make to enable fks?
-
What is the best database technology to use to create a new chat app today?
MySQL + Vitess I noticed Slack gets by using MySQL because they're using Vites. From Slack's post (https://slack.engineering/scaling-datastores-at-slack-with-vitess/) it seems like they choose Vites because it facilitated a smooth transition because it's built on top of MySQL.
- Vitess – Scalable. Reliable. MySQL-Compatible. Cloud-Native. Database
-
How can I avoid duplicate API calls in a serverless infra?
This sounds very similar to the connection pooling done by vitess https://vitess.io/.
-
Scaling Databases at Activision [pdf]
https://github.com/vitessio/vitess/issues/12967
-
Want to avoid MySQL but find PlanetScale really appealing
A lot of this is possible thanks to the magic of Vitess.
-
Vitess 16
"Vitess is a database clustering system for horizontal scaling of MySQL."
https://github.com/vitessio/vitess
What are some alternatives?
jaeger-clickhouse - Jaeger ClickHouse storage plugin implementation
tidb - TiDB is an open-source, cloud-native, distributed, MySQL-Compatible database for elastic scale and real-time analytics. Try AI-powered Chat2Query free at : https://tidbcloud.com/free-trial
uptrace - Open source APM: OpenTelemetry traces, metrics, and logs
supabase - The open source Firebase alternative.
django-simple-history - Store model history and view/revert changes from admin site.
cockroach - CockroachDB - the open source, cloud-native distributed SQL database.
signoz - SigNoz is an open-source observability platform native to OpenTelemetry with logs, traces and metrics in a single application. An open-source alternative to DataDog, NewRelic, etc. 🔥 🖥. 👉 Open source Application Performance Monitoring (APM) & Observability tool
citus - Distributed PostgreSQL as an extension
dbt-clickhouse - The Clickhouse plugin for dbt (data build tool)
go-mysql-elasticsearch - Sync MySQL data into elasticsearch
tsbs - Time Series Benchmark Suite, a tool for comparing and evaluating databases for time series data
kingshard - A high-performance MySQL proxy