Ledgers - When would you even…? Ricardo J. Méndez SAP Inside Track Berlin, 2018 September 1st, 2018 / [email protected] @ArgesRic https://mastodon.social/@ricardojmendez/
@argesric @samsungnext Here’s the plan… ● Give a quick overview of what they are, in case anyone’s not familiar; ● Talk about what I see as the requirements for them to be worth it; ● Give some counterpoints about trade-offs you are making.
@argesric @samsungnext About me Technical Director for Europe at Samsung NEXT in Berlin. We partner with innovators and invest in forward-looking deep-tech companies. Tech guy. Started companies. Done consulting. Seen more gross tool mis-applications than I can remember. Hope I can save you all some time.
@argesric @samsungnext The system needs to… ● Be distributed; ● Have an absence of trust; ● Require consensus; ● Demand disintermediation; ● Keep track of provenance; ● Be auditable.
@argesric @samsungnext Distributed ● Do you want to have data spread across multiple servers? ● Do you want to run queries faster? ● Do you want some redundancy?
@argesric @samsungnext Our system so far… ● Everyone involved has a copy of the data; ● Everyone can try to write to the shared state of the world; ● Every node involved agrees on if the change takes place or not.
@argesric @samsungnext Provenance ● A system where the data can be out of our control, ● Where we don't trust anyone who may be writing to it, ● So we're going to need to design some mechanism to agree on the world's state, ● And which almost refuses to live behind an API wall.
ricardojmendez
takatsunobuhiro
senkin13
nasa_desu
soracom
_kensh
karawoo
shimacos
tomoaki25
bengo4com
oracle4engineer
yayoi_dd
.png){kind=icon}
3playmarketing
jrom
gr2m
davidbonilla
lara
pauljervisheath
geoffreycrofte
jensimmons
ammeep
dougneiner
trishagee
nonsquared
jcasabona