Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Sign up for free
Menu
Search
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Pricing
Search
Sign in
Sign up for free
New Intro to Riak
Search
Joel Jacobson
August 21, 2013
Technology
53
1
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
New Intro to Riak
Joel Jacobson
August 21, 2013
More Decks by Joel Jacobson
See All by Joel Jacobson
Microsoft Azure Meetup
joeljacobson
0
76
CRDTs and Eventual Consistency
joeljacobson
0
76
Killing Pigs and Saving Danish Bacon
joeljacobson
0
81
Conflict-Free Replicated Data Types in Eventually Consistent Systems
joeljacobson
0
130
Intro to Riak
joeljacobson
0
100
Other Decks in Technology
See All in Technology
PfEingのアプローチで働こう
rindrics
0
210
Microsoft 365 Copilot chat -tekoälypalvelun tietosuojaongelmat
hponka
0
620
AI時代のAPI品質を支えるガードレール / API Guardrails for API quality in the AI era
yokawasa
1
210
アプリログインとWeb認証基盤をつなぐ ASWebAuthenticationSession 作法
shimastripe
1
180
Omarchy Quattro の日本語設定周り
simosako
2
140
AIとペアプロを始める。人とのペアプロをやめる。ペアプロの良さを改めて知る。もっと好きになった。 / Rediscovering Pair Programming
honyanya
1
330
振り返りこそエンジニアの本領
negima
0
360
Oracle Cloud Infrastructure IaaS 新機能アップデート 2026/6 - 2026/8
oracle4engineer
PRO
0
140
AIで実装は速くなった。なのにプロダクトは速くならない。職能の壁を越えて価値のフローを設計する
nwiizo
8
7.7k
コーディングエージェントでM5Stack系の開発を少し試した時の話 / M5 Japan Tour 2026 Autumn 東京
you
PRO
0
110
アリアドネの糸と、20年ごとの建て替え ── 長尾真『電子図書館』を、伊勢で読み直す / Rereading Makoto Nagao’s "Electronic Library" in Ise
ykiyota
0
150
20260912_スクラムにジェネラリストは必要か
ryugen04
0
300
Featured
See All Featured
Ethics towards AI in product and experience design
skipperchong
2
370
AI: The stuff that nobody shows you
jnunemaker
PRO
9
980
A designer walks into a library…
pauljervisheath
211
25k
Visualization
eitanlees
152
17k
Documentation Writing (for coders)
carmenintech
77
5.5k
Bioeconomy Workshop: Dr. Julius Ecuru, Opportunities for a Bioeconomy in West Africa
akademiya2063
PRO
1
350
Deep Space Network (abreviated)
tonyrice
0
300
The Psychology of Web Performance [Beyond Tellerrand 2023]
tammyeverts
49
3.5k
Sharpening the Axe: The Primacy of Toolmaking
bcantrill
46
3k
Self-Hosted WebAssembly Runtime for Runtime-Neutral Checkpoint/Restore in Edge–Cloud Continuum
chikuwait
0
780
The Spectacular Lies of Maps
axbom
PRO
1
990
Effective software design: The role of men in debugging patriarchy in IT @ Voxxed Days AMS
baasie
0
510
Transcript
Introduction to Riak 2013
Who am I? Joel Jacobson Technical Evangelist @Basho @joeljacobson
Distributed computing is hard COncurrency scaLIng Latency consIstency avaILabILIty MuLtI
Tenancy faILover SLA’s
What is Riak? Key Value store + extras Distributed /
Horizontally Scalable Fault Tolerant Highly available built for the web
inspired by amazon dynamo white paper released to describe a
database system to be used for their shopping cart Masterless, peer coordinated replication Consistent Hashing Eventually Consistent
Riak Key-value store Simple operations; GET, PUT, DELETE Value is
Opaque, with metadata Extras; Secondary indexes MapReduce full text search
Horizontal Scalability Near linear Scalability Query load and data are
spread evenly Add more nodes and get more; Ops/second storage capacity compute power (mapreduce)
Fault tolerant no Single point of failure (SPOF) All Data
is replicated CLusters self heal; Handoff, Active Anti Entropy cluster transparently survives Node Failure Network partition
Highly Available Any Node Can Serve Client requests Fallbacks are
used when nodes are down Always available for read and write requests Per-request quorums
Quorums n = 3 r / w = 2 R
= 1 - faster response time, less likely consistent r = all - slower response, greater consistency
the ring
Replication replicated to 3 nodes by default (n_val , which
is configurable)
Node fails Request goes to fallback Handoff - data retuned
to recovered node X X X X X X X X hash(“user_id”) Disaster scenario
Automatically repair inconsistencies in data runs as a background process
or Can be configured as a manual process active anti-entropy
Network partitions or concurrent actors modifying the same data Riak
provides two solutions to manage this: Last Write Wins Vector Clocks Conflict resolution
Vector Clocks Every node has an ID Send last-seen vector
clock in every “put” request Can be viewed as ‘commit history’ e.g. Git Lets you decide conflicts
sibling creation 0 3 2 1 Object v1 Object v1
0 3 2 1 Object v1 Siblings can be created by: Simultaneous writes Anti-entropy [{a,3}] [{a,2},{b,1}] [{a,3}] Object v1 Object v1 [{a,2},{b,1}]
storage backends Bitcask Leveldb memory multi
bitcask A fast, append-only key-value store Key space must fit
in memory Suitable for bounded data, e.g. reference data
Leveldb Append-only for very large data sets multiple levels Allows
for more advanced querying (2i) includes compression (Snappy algorithm) Suitable for unbounded data
memory Data is never persisted to disk Definable memory limits
per vnode Configurable object expiry Useful for highly transient data supports secondary indexes
multi Configure multiple storage engines for different types of data
Choose storage engine on per bucket basis
clients apis Protocol Buffers REST based HTTP Interface
client libraries Client libraries supported by Basho: Community supported languages
and frameworks: C/C++, Clojure, Common Lisp, Dart, Django, Go, Grails, Griffon, Groovy, Haskell, .NET, Node.js, OCaml , Perl, PHP, Play, Racket, Scala, Smalltalk
Using Riak as datastore for all back-end systems supporting Angry
Birds Game-state storage, ID/Login, Payments, Push notifications, analytics, advertisements 9 clusters in use with over 100 nodes 263 million active monthly users
Spine2 - storing 80 million+ patient data 500 complex messages
per second 20,000 integrated end points 0% data loss 99.9% availability SLA
Push to talk application Billions of requests daily > 50
dedicated servers Everything stored in Riak
MDC Allows data to be replicated between clusters in different
data centers real-time and full sync uni-directional or bi-directional replication global load-balancing backups
riak-cs S3 compatible object store Supports Objects of Arbitrary Content
Type Up to 5TB multi-tenancy Per-tenant usage data and statistics on network I/O supports MDC
try it? http://docs.basho.com/riak/latest/references/appendices/ community/Sample-Applications/ https://github.com/basho/riak-dev-cluster
thanks
[email protected]