This document summarizes RON (Replicated Object Notation) and compares it to JSON for use in syncing data. It argues that while JSON is easy to read, RON has advantages over JSON for syncing due to its support for typing, identity, versioning and addressing which enable conflict-free replication. The document explores these concepts through examples and discusses how RON is based on CRDTs which allow for conflict-free replicated data types.
1 of 17
Download to read offline
More Related Content
Reactive17wide
1. RON: REPLICATED OBJECT NOTATION
WHY JSON IS NOT SO GOOD (FOR SYNC)
VICTOR GRISHCHENKO, PHD
REACTIVE CONF 2017, BRATISLAVA
2. PROOF
SYNC IS HARD, JSON IS EASY
Contradiction
*db#test$srvr@)1-client:)2+srvr!.
#)3+client!.
*lww#)3+client@)3+client!:a'b'.
*db#test$srvr@)1-client
:EOF$~~~~~~~~~~!.