GitHub - rockwotj/chorus: A fast, single-writer write-ahead log on Google Cloud Storage · GitHub
/" data-turbo-transient="true" />
Skip to content
Search or jump to...
Search code, repositories, users, issues, pull requests...
-->
Search
Clear
Search syntax tips
Provide feedback
--><br>We read every piece of feedback, and take your input very seriously.
Include my email address so I can be contacted
Cancel
Submit feedback
Saved searches
Use saved searches to filter your results more quickly
-->
Name
Query
To see all available qualifiers, see our documentation.
Cancel
Create saved search
Sign in
/;ref_cta:Sign up;ref_loc:header logged out"}"<br>Sign up
Appearance settings
Resetting focus
You signed in with another tab or window. Reload to refresh your session.<br>You signed out in another tab or window. Reload to refresh your session.<br>You switched accounts on another tab or window. Reload to refresh your session.
Dismiss alert
{{ message }}
rockwotj
chorus
Public
Notifications<br>You must be signed in to change notification settings
Fork
Star<br>15
main
BranchesTags
Go to file
CodeOpen more actions menu
Folders and files<br>NameNameLast commit message<br>Last commit date<br>Latest commit
History<br>3 Commits<br>3 Commits
.github/workflows
.github/workflows
artifacts
artifacts
bench
bench
docker
docker
rust
rust
.dockerignore
.dockerignore
.gitignore
.gitignore
LICENSE
LICENSE
README.md
README.md
Taskfile.yml
Taskfile.yml
rust-toolchain.toml
rust-toolchain.toml
View all files
Repository files navigation
Chorus
Chorus is a single-writer write-ahead log built directly on Google Cloud<br>Storage. If your database already lives in GCP, three zonal Rapid buckets and<br>one regional bucket give you a durable, zone-fault-tolerant WAL with no<br>Apache Kafka, no etcd, and no extra servers to operate. The buckets are the log.
Building robust, scalable, and cheap storage on object stores comes at a cost:<br>write latency. Reads can hide behind a cache; durability-critical writes cannot.<br>Chorus closes that gap. A single Rapid bucket lives in only one availability<br>zone, so Chorus replicates the log across a strict majority of zonal buckets<br>(three in the common deployment), commits each record once any two report it<br>durable, and survives the loss of any one zone. Its entire control plane is a<br>single regional GCS object, a compare-and-swap register kept off the per-record<br>commit path, so commits run at zonal-bucket latency.
For 4 KiB records committed individually in-region, Chorus commits with a<br>1.71 ms median and 2.74 ms p99, both below the median of Google Cloud's<br>synchronously-replicated regional block storage. It delivers regional durability<br>at single-zone write latency, backed by a machine-checked correctness argument:<br>the protocol is specified and model-checked in P for safety and liveness, the<br>production Rust client is exercised under deterministic simulation testing, and<br>its traces are replayed against the P model with PObserve to check the<br>implementation against the specification.
To learn more about the story behind Chorus, check out the introductory blog post.
About
A fast, single-writer write-ahead log on Google Cloud Storage
Resources
Readme
License
Apache-2.0 license
Uh oh!
There was an error while loading. Please reload this page.
Activity
Stars
15<br>stars
Watchers
watching
Forks
forks
Report repository
Releases
tags
Packages
Uh oh!
There was an error while loading. Please reload this page.
Contributors
Uh oh!
There was an error while loading. Please reload this page.
Languages
Rust<br>79.8%
Gnuplot<br>16.2%
Python<br>2.6%
Java<br>1.2%
Other<br>0.2%
You can’t perform that action at this time.