1. What are the contributions in "Replicated data types: specification, verification, optimality" ?
To fill in this gap, the authors propose a framework for specifying replicated data types using relations over events and verifying their implementations using replication-aware simulations.. The authors also present a novel technique for obtaining lower bounds on the worstcase space overhead of data type implementations and use it to prove optimality of 4 implementations.. Finally, the authors show how to specify consistency of replicated stores with multiple objects axiomatically, in analogy to prior work on weak memory models.
read more
2. What future works have the authors mentioned in the paper "Replicated data types: specification, verification, optimality" ?
Although their work marks a big step forward, it is only a beginning, and creates plenty of opportunities for future research.. In the future the authors would also like to study more data types, such as lists used for collaborative editing [ 32 ], and to investigate metadata bounds for data type implementations other than state-based ones, including more detailed overhead metrics capturing optimizations invisible to the worst-case overhead analysis.. Finally, by bringing together prior work on shared-memory models and data replication, the authors wish to promote an exchange of ideas and results between the research communities of programming languages and verification on one side and distributed systems on the other.
read more




![Fig. 17, [12, §A] new‡ Θ̂(n lgm) Ω̂(n lgm)](/figures/fig-17-12-ssa-new-th-n-lgm-n-lgm-1kfchwz2.png)
![Figure 9. Proof obligations for abstract methods. Free variables are implicitly universally quantified and have the following types: C,C′ ∈ CEx[x]∩ T , D ∈ DEx, r ∈ ReplicaID, e ∈ Event, (R, T ) ∈ Config.](/figures/figure-9-proof-obligations-for-abstract-methods-free-1f77rnij.png)