Mahmut Bulut (@vertexclique)
Mahmut Bulut
@vertexclique on internets.
Making
are not semi-hard. It is hard.
From zero to hero… all included in Artillery
Everything should be component based. Everything is
Dist. sys. engineers best at that.
Either zeroconf or another way you will discover services.
Artillery comes with built-in Zeroconf with both pure broadcast and UDP-anycast based methods.
NEXT UP: Forming a Cluster
REQUIREMENTS
Guess which protocol suites suit to it?
Guess which protocol suites suit to it?
KAOS: Chaotic Testing Harness
TESTING
~~~ IN ACTION ~~~
Artillery comes with the mentioned membership protocol.
In the future for distributed actors, we can use gossip to exchange messages.
NEXT UP: Data Replication
REQUIREMENTS
Actual mixed workloads are like: 60% read, 25% update, 10% insert, and 5% scan
* YCSB mixed workload definition
*
* Wu, Y., Arulraj, J., Lin, J., Xian, R., & Pavlo, A. (2150). An Empirical Evaluation of In-Memory Multi-Version Concurrency Control.
It is hard to make "%60 read" successful with low latency in these circumstances with geo distribution.
Workloads are read mostly.
Solution:
CHAIN REPLICATION
* Ordinary chain replication runs with tail queried reads
* Advanced mode (apportioned queries) runs with all nodes enabled with reads
Even in synchronous mode it is
16000 ops/sec
Rust is my comrade in arms. Can't imagine how fast this will be with async code & executors.
TO SUM UP ARTILLERY IS