claudie
Xline
claudie | Xline | |
---|---|---|
5 | 16 | |
481 | 521 | |
6.0% | 3.1% | |
9.0 | 9.8 | |
8 days ago | 5 days ago | |
Go | Rust | |
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.
claudie
- Multi-region multi-cloud cluster. Best practices?
-
Simplifying Kubernetes Cluster Management with Claudie and Sveltos
Claudie simplifies the process of programmatically establishing Kubernetes clusters across multiple cloud vendors and on-premises datacenters. It provides a centralized management interface for provisioning and managing clusters, eliminating the need for manual configuration and maintenance. Claudie's capabilities include:
-
Best cross cloud managed Kubernetes that also supports bare metal?
I'm one of the authors of https://github.com/berops/claudie
-
Claudie is a managed Kubernetes for Hetzner, now coming with Cluster Autoscaler
There's also Hetzner bootstrapping information specifically here: https://github.com/berops/claudie/blob/master/docs/input-manifest/providers/hetzner.md
Xline
- Multi-region multi-cloud cluster. Best practices?
- Show HN: A Geo-Distributed KV Store for Metadata Management
-
Introduction to Curp Protocol
The CURP paper doesn't define a new leader election algorithm and presumes you use an existing one like raft. Xline is using raft based on the readme
https://github.com/xline-kv/Xline/tree/master/curp/tla%2B
warning, I skimmed and ctrl-fd for "leader election"
- Show HN: Geo-Distributed Metadata Management System
- Show HN: Xline0.4.0: Geo-Distributed KV Store for Metadata Management
-
Do people care about latency in blockchain?
Hi! We are developing an distributed KV database named Xline, which uses the CURP protocol to achieve up to a 50% reduction in latency compared to traditional distributed databases. As someone who is not well-versed in blockchain technology, I am curious to know whether low latency is the primary concern or if other factors are more important in this field?
-
Xline V0.3.0: A Geo-distributed KV Store For Metadata Management Built in Rust
Implement a storage engine layer to abstract the concrete storage engine, like rocksdb , and enable upper layer storage function (#185, #187)
- Show HN: Xline v0.3.0: A Geo-Distributed KV Store for Metadata Management
- Xline v0.2.0: Rust Powered Geo-distributed KV Store For Metadata Management
- Xline: A new geo-distributed KV store for metadata management
What are some alternatives?
rainbond - No need to know Kubernetes' cloud native application management platform | 不用懂 Kubernetes 的云原生应用管理平台
roapi - Create full-fledged APIs for slowly moving datasets without writing a single line of code.
kubevela - The Modern Application Platform. [Moved to: https://github.com/kubevela/kubevela]
raft.tla - TLA+ specification for the Raft consensus algorithm
OpenStack-Guide - OpenStack Guide
OpenShift-Guide - OpenShift Guide. Learn about the Red Hat OpenShift Container Platform, Data Science, Code Ready Containers, Podman, Buildah, and Kubernetes.
k3sup - bootstrap K3s over SSH in < 60s 🚀
kubefirst - The Kubefirst Open Source Platform
elcarro-oracle-operator - El Carro is a new project that offers a way to run Oracle databases in Kubernetes as a portable, open source, community driven, no vendor lock-in container orchestration system. El Carro provides a powerful declarative API for comprehensive and consistent configuration and deployment as well as for real-time operations and monitoring.