Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/jamf/regatta
Regatta is a distributed key-value store. It is Kubernetes friendly with emphasis on high read throughput and low operational cost.
https://github.com/jamf/regatta
database distributed-systems go key-value kubernetes raft
Last synced: about 2 months ago
JSON representation
Regatta is a distributed key-value store. It is Kubernetes friendly with emphasis on high read throughput and low operational cost.
- Host: GitHub
- URL: https://github.com/jamf/regatta
- Owner: jamf
- License: mit
- Created: 2022-11-01T16:11:06.000Z (almost 2 years ago)
- Default Branch: master
- Last Pushed: 2024-06-26T06:54:15.000Z (3 months ago)
- Last Synced: 2024-06-26T08:02:05.733Z (3 months ago)
- Topics: database, distributed-systems, go, key-value, kubernetes, raft
- Language: Go
- Homepage: https://engineering.jamf.com/regatta
- Size: 2.99 MB
- Stars: 63
- Watchers: 1
- Forks: 5
- Open Issues: 17
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Contributing: docs/contributing.md
- License: LICENSE
- Codeowners: CODEOWNERS
- Security: security/tls.go
Awesome Lists containing this project
- awesome-go - regatta - Fast, simple, geo-distributed KV store built for cloud native era. (Database / Databases Implemented in Go)
- awesome-ccamel - jamf/regatta - Regatta is a distributed key-value store. It is Kubernetes friendly with emphasis on high read throughput and low operational cost. (Go)
README
# Regatta
[](https://github.com/jamf/regatta/releases)
[](https://coveralls.io/github/jamf/regatta)
[](https://goreportcard.com/report/github.com/jamf/regatta)
[](https://github.com/jamf/regatta/graphs/contributors)
[](LICENSE)
**Regatta** is a distributed ETCD inspired key-value store. Regatta is designed to operate eiter as a standalone node,
standalone cluster or in Leader - Follower mode suited for distributing data in distant locations. e.g. in different
cloud regions.
While Regatta maintains many of ETCD features there are some notable differences:
* Regatta is designed to store much larger (tens of GB) datasets and also provide iterator-like API to query large
datasets.
* Regatta prioritize speed and performance over some more advanced ETCD features like Watch API, or Leases.
* Regatta support multiple separate keyspaces called tables which operate individually.
## Production readiness
* Even though Regatta has not yet reached the 1.0 milestone it is ready for a production use.
* There might be backward incompatible changes introduced until version 1.0, those will always be flagged in the release
notes.
* Builds for tagged versions are provided in form of binaries in GH release, and Docker images.
* Tagged releases are suggested for production use, mainline builds should be used only for testing purposes.
## Why you should consider using Regatta?
* You need to distribute data from a single cluster to multiple follower clusters in edge locations.
* You need a local, persistent, cache within a data center and reads heavily outnumber writes.
* You need a pseudo-document store.
## Documentation
For guidance on installation, deployment, and administration,
see the [documentation page](https://engineering.jamf.com/regatta).
## Contributing
Regatta is in active development and contributors are welcome! For guidance on development, see the page
[Contributing](https://engineering.jamf.com/regatta/contributing).
Feel free to ask questions and engage in [GitHub Discussions](https://github.com/jamf/regatta/discussions)!