Dor Laor, ScyllaDB

1. 10 devops-friendly database must-haves
Dor Laor@ScyllaDB

2. What’s a devops-friendly must-have?
Always-on (Multi zone/DC)
Automation friendly
Fear of change should be ~zero
Git push and see if it falls?
Risk should be capped
downgrade-able. How do you do it?
No Siloization

3. THE POWER OF
CASSANDRA AT
THE SPEED OF REDIS
<1.8e6 op/s/s>
@ScyllaDB

4. 10. DevOps 101’s
Secure - Authentication
Encryption {client-node, node-node, data at rest}
Key mgmt
Multi platform - Docker, VMs, byte code, etc
Auditable, Logging - Self explanatory
Traceable - Yeah

5. 9. Backup/restore
Sure, that’s why they invented S3
Wrong
Eventual consistent backups == Ouch
Distributed snapshots with eventual consistency is challenging
Restore - Well, should it just work?
Will it work on a remote zone?
Will it work on different set of servers/shards

6. 9. Scale
Scale up - 5k - 50k op/s is quite poor
Lack of scale up will force you to manage hundreds of nodes
and touch base with rough product edges - << MTBF >>
Poor scale up means poor engineering - Mechanical Sympathy
No additional caches such as Redis, memcache, etc.
You’d like to use fancy maps, views, etc, don’t you?

7. 9. Scale (cont’)
Scale out - everybody has a limit
Must-have for high availability and DR
Better be symmetric (otherwise you calculate the proportion)

8. What happened?#$%

9. 8. Consistent Tail Latency
Low average latency is so yesterday
GC will make you pay and the currency is your bed time

10. 8. Latency : Coordinated Omission

11. 7. Automatic XYZ
(NO!) Tunables - GC, OS, ..
Elastic - fully auto scale, including data mgmt
Some DBs cannot add multiple nodes at once
Auto sharding, re-sharding, vnodes,

12. 6. Extendable
Export/Import - CSV, JSON, parquet, ..
UDF, Lua scripts, Stored-procedures
Building block - not a one trick pony - time series,
graph DBs, metrics, ..

13. 5. Resilient @aphyr
What if we cut the network here?
What if we isolate a master?
What if there's no connected majority?
What if there's asymmetric connectivity?
How about intermittent connectivity?
What if clocks are unsynchronized?
What if a node pauses for a few minutes and then comes back?

14. 4. Integrated with Big Data
Aggregations, mapreduce closer to the data!
Since you like to use Spark
analytics, Elastic Search, etc
4.1 Not integrated with
Big Data (Self contained)

15. 3. Isolated Test&Dev Environment
Wouldn’t it be nice to proxy/duplicate the data stream:
Test bed
Development setup
New version

16. 2. Multi tenancy
Micro services trigger services proliferation
Multiple database clusters are wasteful
However, SLA differs in so many ways.
Solution: Multi tenancy in the database layer.
Similar to OS resource group (yes, docker)

17. 1. OPEN
This is where it begins
and ends

18. SCYLLA, NoSQL GOES NATIVE
Thank you.

19. BACKGROUND
SQL:
Structured,
no scale
Document store:
No structure
Some scale
Column store:
Some structure
Scale out
Awesome HA/DR
Key-value:
Simple
Scale
Not a real DB