Skip to content

Middleware eventual consistency

Andrew Gaul edited this page May 14, 2016 · 1 revision

S3Proxy can model eventually consistent behavior of object stores by using two storage backends. Client writes go into the first object store and reads come from the second object store. An asynchronous process copies objects from the former to the latter after a configurable interval. An example properties file:

s3proxy.endpoint=http://localhost:8081
s3proxy.authorization=aws-v2
s3proxy.identity=local-identity
s3proxy.credential=local-credential
s3proxy.eventual-consistency=true
s3proxy.eventual-consistency.delay=5  # time in seconds
s3proxy.eventual-consistency.probability=1  # percentage expressed as a number between 0.0 and 1.0

jclouds.provider=transient
jclouds.identity=remote-identity
jclouds.credential=remote-credential

alt.jclouds.provider=transient
alt.jclouds.identity=remote-identity
alt.jclouds.credential=remote-credential