rawkv
raft
rawkv | raft | |
---|---|---|
2 | 4 | |
11 | 535 | |
- | 6.7% | |
1.4 | 8.8 | |
about 1 year ago | 8 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.
rawkv
-
Running 2 web apps in one application using Go Routines
For example in a distributed database like this, each node of the database has to start one server listening to a port to serve database users’ requests to CRUD data, and start another server on a different port to serve data replication requests between nodes. And you want only one main function for the code running on each node, so using a goroutine like what you shared makes perfect sense.
-
A cloud-native distributed key-value database
Would like to share this project I wrote some time ago when I first time learned Go. It familiarizes me with core features of Go and makes me love the language even more. I strived to make the code well structured and documented so that it can benefit more people who are interested in Go (or databases). Any suggestions/advices are warmly welcomed!
raft
-
On Implementation of Distributed Protocols
etcd Raft — a library for maintaining replicated state machines (written in Go);
- Leader election library
-
Implementing a distributed key-value store on top of implementing Raft in Go
Have you seen this implementation? https://github.com/etcd-io/raft. I’ve used this as a starting point for our consensus with various services.
-
"In HPA, multiple pods may perform duplicate operations and cause data inconsistency?"
This is usual in parallel and distributed systems. For k8s, I recommend you either use Apache Zookeeper to coordinate “logical locks” for operations across pods or use the RAFT consensus protocol for scenarios where you need coordination amongst pods. For context, k8s itself uses the RAFT consensus protocol for etcd; see https://github.com/etcd-io/raft
What are some alternatives?
sealer - Build, Share and Run Both Your Kubernetes Cluster and Distributed Applications (Project under CNCF)
rqlite - The lightweight, distributed relational database built on SQLite.
regatta - Regatta is a distributed key-value store. It is Kubernetes friendly with emphasis on high read throughput and low operational cost.
etcd - Distributed reliable key-value store for the most critical data of a distributed system
Atomix - A Kubernetes toolkit for building distributed applications using cloud native principles
easegress - A Cloud Native traffic orchestration system
dragonboat - A feature complete and high performance multi-group Raft library in Go.
kivi - Dynamo-inspired distributed leader-less key-value database that has no unique features and no apparent reason to exist
etcd - Distributed reliable key-value store for the most critical data of a distributed system [Moved to: https://github.com/etcd-io/etcd]
leaderelection