2023 Facemoji State of Emoji Report2023 Facemoji State of Emoji Report

ArpanaRawat2 9 views 44 slides Jul 08, 2024
Slide 1
Slide 1 of 44
Slide 1
1
Slide 2
2
Slide 3
3
Slide 4
4
Slide 5
5
Slide 6
6
Slide 7
7
Slide 8
8
Slide 9
9
Slide 10
10
Slide 11
11
Slide 12
12
Slide 13
13
Slide 14
14
Slide 15
15
Slide 16
16
Slide 17
17
Slide 18
18
Slide 19
19
Slide 20
20
Slide 21
21
Slide 22
22
Slide 23
23
Slide 24
24
Slide 25
25
Slide 26
26
Slide 27
27
Slide 28
28
Slide 29
29
Slide 30
30
Slide 31
31
Slide 32
32
Slide 33
33
Slide 34
34
Slide 35
35
Slide 36
36
Slide 37
37
Slide 38
38
Slide 39
39
Slide 40
40
Slide 41
41
Slide 42
42
Slide 43
43
Slide 44
44

About This Presentation

2023 Facemoji State of Emoji Report


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

Demo time

Deeper dive

What's next

+ + + + +

® scriia

< 6.@ ScyllaDB Releases Were Good

3x4vepuVMs 3xBvcpuVMs 3X 16-vepuVMs 3x32vepuVMs 3x 64vcpuVMs — 3.x 12B-vepu VMs
1Bkeys 78 keys 4B keys BB keys 168 keys 328 keys

i of
\=

disrupt_mgmt_repair_cli

E) SCYLLA

ScyllaDB < 6.0 Problems

+ 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

Escrita

fam eventual

Escrita

ScyllaDB 6.0 Value

Elasticity

+ Faster hootstrap/operations
+ Incremental bootstrap
+ Concurrent node operations

Speed

+ Streaming sstables - 30x faster
+ Load balancing of tablets Consistency
+ Small tables fit in few (single) nodes

@scyita

Simplicity

+ Decouple topology operations
+ Transparent cleanups
+
+

Semi transparent repairs
Parallel maintenance operations

TCO

+ 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

+ + + +

Escrita

CREATE TABLE system. tablets (

table_id uuid,

last_token bigint,

Keyspace_name text static,
replicas listétuplecuuid, int>>,
new_replicas listetuplecuuid, ints>,
session uuid,

stage text,

transition text,

table_name text static,
tablet_count int static,

PRIMARY KEY (tablo_id, last_token)

Tablets - Balancing

— 90 9

oo

Depends on fault-tolerant,
reliable, and fast topology
‚changes.

© SCYLLA

Implementation - Load Balancer

+ Hosted on one node

+ But can be migrated freely if the node is down
+ Synchronized via Raft
+ Collects statistics on tables and tablets

+ Migrates to balance space

+ Evacuates nodes to decommission

+ Migrates to balance CPU load

+ Rebuilds and repairs

E
LP

Escrita

Tablet Scheduler Get!

Scheduler globally controls movement,
maintenance operation on a per tablet basis

schedule schedule
I 1

:
|

1
1
1
1
1
1
1
1
1
1

|
|
|

@ scyita

Tablets

Resharding is cheap.
SStables split at tablet boundary.
Reassign tablets to shards (logical operation).

® scruun

Tablets

Cleanup after topology change is cheap.
Just delete SSTables. Runs automatically,

under the hood

XA

® scriia

Tablets - Streaming (Enterprise)

Send files over RPC. No per
schema, per row processing.
Up to 30x faster, saturate links.

Driver Support

+ Drivers are tablet-aware
+ But without reading the tablets table
+ Driver contacts a random node/shard

+ On miss, gets updated routing information for
that tablet

+ Ensures fast start-up even with 100,000 entries
in the tablets table

@scyita

Authentication and Service Levels on

ScyllaDB 5.x was Manual

ScyllaDB 6.x:
+ Automatically replicated on every node
+ Linearizable with CREATE/DROP

+ No denial of service if a node is down

@scyita

Raft

What's Coming

Tablets - Repair - Fire & Forget

+ Continuous, transparent controlled by the load balancer
+ Auto GC grace period

E) SCYLLA

Consistent
Elasticity =

Poll

How long does it take for you to scale
your existing database?

@ scyita

ONLINE | OCT 23 + 24, 2024

P99 CONF

aDB \ All Things Performance

engineering

scylladb.com/category/engineering

E) SCYLLA

Thank you

for joining us today.

f @scyliadd (E soylladb/

Y ascylladb Ak slack scylladb.com

New metrics in keyspace dashboard

@ seylla-monitoring provides an updated dashboard that shows tablets over time per instance

and tablet count per instance at the moment

ScyllaDB ENGINEERING SUMMIT 2024 40 \

Write workload

ScyllaDB

Growing a cluster - Tablets



ur

@scyita

Growing a cluster - Tablets

~~

ur

@scyita

Growing a cluster - Tablets

@ scyita
Tags