2023 Facemoji State of Emoji Report2023 Facemoji State of Emoji Report
ArpanaRawat2
9 views
44 slides
Jul 08, 2024
Slide 1 of 44
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
About This Presentation
2023 Facemoji State of Emoji Report
Size: 969.64 KB
Language: en
Added: Jul 08, 2024
Slides: 44 pages
Slide Content
dl @scyiia
ScyllaDB Fast Forward:
True Elastic Scale
Dor Laor, CEO and Co-Founder, ScyllaDB
Felipe Cardeneti Mendes, Solutions Architect++, SoyllaDB
Poll
How often do you scale your database?
(2 SCYLLA
Presenters
Felipe Cardeneti Mendes, Solutions Architect
+ Puppy Lover
+ Open Source Enthusiast
+ ScyllaDB passionate!
Dor Laor, CEO and Co-Founder
+ Puppy Lover
+ Open Source, snowboard and MTB Enthusiast
+ ScyllaDB passionate!
Why ScyllaDB?
The power of Cassandra at the speed of Redis with the usability of DynamoDB
Best Price/Performance in the industry Auto-tune - out of the box performance
Best High Availability in the industry Compatible with Cassandra & DynamoDB
[ Best Disaster Recovery in the industry ] | No Lock-in |
Best scalability in the industry Open Source Software
aws o
LL) kubernetes A Azure
sd D À Gone csshas e,
Escrita
+408 Gamechangers Leverage ScyllaDB
@oiscora GSAS @Expedio STRAVA hulu Denk
Eubi @ sharechat COptimizeiy TRACTIAN &Zillow
E RisingWave coMGAST Esiotinema 4 paloalto’
“F Fanaties
AEVERSINGLABS
zn
e Urmeccre Grad SADA @ Homar
PU nauto @ Tripadvisor ticketmaster’ @crypto.com
@scyita
Agenda
Wasn't ScyllaDB elastic before?
The value proposition
+ Eventual Consistency of cluster metadata
+ Great architecture for scalable, partition-tolerable, widely distributed DB
+ But
+ Topology changes are allowed one-at-a-time
+ Rely on 30+ second timeouts for poor's man linearizability
+ Node failed/down block scale
+ Streaming time is a function of the schema - parsing partitions
+ Additional complex operations: Cleanup, rebuild, etc
+ Shrink free space
+ Reduce static, over provisioned deployments
Demo Time!
a
@scyiia
Theory Behind Tablets
Node 1 Node 2
@scyita
Raft- Consistent Metadata
Protocol for state machine replication
Total order broadcast of state change commands
4
Escrita
Linearizable Token Metadata
node A
node B
node C
. bootstrap
® scyita
Changes in the Data Plane
+
Fencing - each write is signed with topology version
+
If there is a version mismatch, the write doesn't go through
Replica
Coordinator
Topology
coordinator
Escrita
Linearizable Schema Version
sx 6.x:
oni 66066668
Hash-based schema version TimeUUID-based Schema version
No re-hash of the entire schema on change
10x less CPU with large schemas.
@ scyita
J SCYLLA
Erin ther gros
ee
ee
tout
ae
replica replica ropa
ar — ine
tablet | tablet | tablet
Colossus Colossus Colossus
Om Caner Qu Canter Y Du Carter z
Consistent Metadata & Tablet Journey
— ES
A
di
Sale topalegy £
changes
@ scyira
Implementation - Metadata
+ Introduce a new layer of indirection - the tablets table
+ Each table has its own token range to nade mapping
+ Mapping can change independently of node addition
and removal
+ Different tables can have different tablet counts
+ Managed by Raft
@scyita
Implementation - Data Path
+ Each tablet replica is isolated into its own Ga =
memtable+ SSTables
+ Forms its own little Log-Structured Merge Tree Cut ous
+ With compaction and stuff
+ Can be migrated as a unit
+ Migration: copy the unit N Men
+ Cleanup: delete the unit
+ Split/merge as the table grows/shrinks
it
i
@scyita
Standard Tables kr E
Sharding function generates
ai good load distribution between
Raft Tables < Y
RAFT q
No. 299
7 tablet i i | \ tablet
replica replica
tablet 7
® scyita
The Tablets Table
+ Source of truth for the cluster
+ How many tablets for each table
Token boundaries for each tablets
On which nodes and shards do we have replicas
What kind of transition the tablet is undergoing
Which nodes and shards will host tablet replicas
after the transition
+ Managed using the Raft protocol
+ Replicated on every node