orchestrator
discussion
| orchestrator | discussion | |
|---|---|---|
| 3 | 4 | |
| 5,492 | 79 | |
| 0.7% | - | |
| 0.0 | 1.8 | |
| 15 days ago | almost 2 years ago | |
| Go | ||
| 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.
orchestrator
-
MariaDB Cluster Management
https://github.com/openark/orchestrator might be something for you. I dont know if it works with Mariadb, but it is made for regular old MySQL.
- Vitess 11
-
MYSQL Operator: A MYSQL ❤ affair with Kubernetes
The whole infrastructure runs on top of Kubernetes, along with **Github Orchestrator** which is an open-source tools that provides a pretty intuitive UI, also we have the MYSQL Operator which does the actual heavy lifting & provisions various MySQL Nodes & Services, what’s even greater is that each MYSQL Instances has mysqld-exporter service running which can be used for monitoring.
discussion
-
UUIDv7 is coming in PostgreSQL 17
> Integers don't scale because you need a central server to keep track of the next integer in the sequence.
They most assuredly do scale. [0]
Also, Slack is built on MySQL + Vitess [1], the same system behind PlanetScale, which internally uses integer IDs [2].
[0]: https://www.enterprisedb.com/docs/pgd/latest/sequences/#glob...
[1]: https://slack.engineering/scaling-datastores-at-slack-with-v...
[2]: https://github.com/planetscale/discussion/discussions/366
-
HELP: GitHub, PlanetScale(MySQL), and Dashboards
Some context avail at https://github.com/planetscale/discussion/discussions/186
- How do I maintain referential integrity?
-
Vitess 11
Please prioritize the standard connection string access method: https://github.com/planetscale/beta/discussions/15
This single feature would open up a lot of usage for me and many others I know.
What are some alternatives?
pg_auto_failover - Postgres extension and service for automated failover and high-availability
mysql-operator - Asynchronous MySQL Replication on Kubernetes using Percona Server and Openark's Orchestrator.
patroni - A template for PostgreSQL High Availability with Etcd, Consul, ZooKeeper, or Kubernetes
binlog - mysql binlog replication protocol in golang
rclone - "rsync for cloud storage" - Google Drive, S3, Dropbox, Backblaze B2, One Drive, Swift, Hubic, Wasabi, Google Cloud Storage, Azure Blob, Azure Files, Yandex Files
thanos - Highly available Prometheus setup with long term storage capabilities. A CNCF Incubating project.
discussion - Discussion repository for Forth enthusiasts.